requirements (glib >= 1.2.4 gtk+ >= 1.2.4) not met

[Peter Garrett]

On Sat, 24 Jun 2006 13:32:51 +0200
Duncan Lithgow <duncan at lithgow-schmidt.dk> wrote:

> > You might save yourself a lot of time and trouble by running
> > 
> > sudo apt-get build-dep kino
> I don't seem to have a man page for build-dep so maybe you can tell me
> how it works? I have kino 0.8 installed and I've downloaded 0.9, so
> what's build-dep actually doing? I mean kino 0.8 works, so how can it be
> that I need to get more dependencies (14+ MB worth...)?

Well, it's part of the many options for apt-get. You can look at the
apt-get howto:

http://www.debian.org/doc/manuals/apt-howto/index.en.html

With specific reference to:
http://www.debian.org/doc/manuals/apt-howto/ch-sourcehandling.en.html

Or, install the apt-howto package. After installing that, typing
"apt-howto" in a terminal should open it in your browser - you can
bookmark it, and have it there for reference whether on or off line...

The idea is that running

sudo apt-get build-dep kino

pulls in all the requirements for *building* the package - these are not
present when you have a pre-built binary version, which is what you have
for 0.8, unless you built it yourself. Of course, for a new version there
may be additional dependencies, but in most cases they will be the same.
For instance, I compiled the latest fluxbox, which isn't in the repos for
dapper, by first issuing " sudo apt-get build-dep fluxbox", then
proceeding with the compile.

The reason you need more dependencies is that the kino 0.8 you have is
purely pre-compiled, whereas to compile your own you need the headers and
development packages relevant to *building* the package - as I said,
usually of the form lib*-dev. "apt-get build-dep kino" will install them
for you - with the caveat that if the new version requires additional or
updated versions not in the repos, apt obviously can't find those for you.

Peter