In the case of ImageMagick, the GNOME dependency seems to be "librsvg2" which requires lots of GNOME packages. But ImageMagick does not require any GNOME libraries to work, so in my opinion it would be better to have two packages: imagemagick (without the svg support) and an imagemagick-gnome (which heavily dependes on GNOME libraries), which makes more sense if you don't want to compile a lot of extra libraries.

Jose A., decompress the following attachment and copy the files into / sw/fink/dists/local/main/finkinfo and then fink index. This revision does not support svg (gnome dependencies) and djvu formats (qt3 dependencies), but it has less dependencies.

Aleix

Attachment: imagemagic.tar.gz
Description: GNU Zip compressed data



On Jan 14, 2008, at 11:37 AM, Daniel Macks wrote:

You can 'fink show-deps PACKAGE' to see the immediate (explicit)
dependencies of PACKAGE. I bet you'll find that the "problem" from
your perspective is not wine itself (or imagemagick itself), which may
have a small list of dependencies that all see reasonable. Rather, one
of those innocuous-sounding deps may need some huge set of libraries
to support it. Consider that there are lots of independent pieces of
reusable code instead of "the thing you want" containing everything in
its single (and huge) binary...the code's all gotta be present and
compiled, it's just an issue of where and how.

"It's a large number of packages if you have a relatively bare-bones
system", but that's how open-source is: each thing is a relatively
small layer on top of several lower-level things (and so on down the
chain). If you have never needed any of the lower-level things, they
will all have to be installed in order to use some very high-level
thing. Then when you need some other high-level thing, all those
dependent libraries are just re-used. I just installed the full
mozilla suite, and I had to install zero additional things (!) because
all of its dependencies (and their dependencies, and so on) were
already installed for other stuff I was using.

The two cases at hand provide good examples actually. Imagemagick just
needs a few image and font-rendering libraries, but one of those is
written on top of several gnome packages, each of which has more gnome
to support it. Conversely, is it really surprising that a whole Win32
emulation system involves graphics, sound, text, file-format support,
system services, widgets, and security?

dan
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to