Carol Spears <[EMAIL PROTECTED]> writes:
> debian sid has given me some broken g* things. i was playing
> dselect games to try to get things to install correctly.
> at one point, i attempted to install the gtk2 stuff i needed by
> requesting gimp2. this is the listing that prompted these questions
> and i understand that it could be debian specific answers.
I guess you requested "gimp" since that's the name of the debian
package that holds gimp-2.0 (at the moment).
> asking dselect gave me a dependency list that was astounding
> compared to what i need to build the gimp from the cvs sources.
The debian package includes basically all plug-ins that we ship in the
standard gimp tarball. For that reason it depends on a number of
libraries that are optional when you are compiling from source.
> all of that libgail and sax stuff is to build the docs? is that the
> only way for the documentation to work for special devises and the
> other accessibily issues?
No, there are no dependencies on tools to build docs. Building docs is
part of the build process and a binary debian packages has runtime
So, let's examine where the dependencies come from. Here's the list of
dependencies (obtained using apt-cache showpkg gimp):
And here's an attempt to break this up into dependencies of the core
and plug-in dependencies:
Dependencies of the GIMP w/o any modules or plug-ins:
Some other dependencies with associated plug-ins. Dependencies that
are already required by the GIMP core have been omitted:
I don't think I need to explain that the png plug-in needs libpng and
If the debian gimp packages was split into smaller packages, some of
this dependency nitemare could be avoided. But it would of course add
some extra work for the package maintainers and I am not sure if it
would be worth the hassle. Especially since most people already have
most of these packages installed because they are needed by lots of
Anyway, I hope my little dependency charts helped to clear things up a
bit. I am sure the dependencies could have been illustrated better,
for example like this PDF that shows the (slightly broken)
dependencies of gimp2 in darwinports:
Gimp-developer mailing list