On Mon, Jan 05, 2009 at 03:53:24PM +1100, James Bunton wrote:
> On Sun, Jan 04, 2009 at 10:52:03PM -0500, Daniel Macks wrote:
> <snip>
> > For cases where the dependencies (NB: I'm lumping Depends and
> > BuildDepends together per others' comments) are only for front ends,
> > those can sometimes be spun off into separate .info files. We do have
> > several successful cases of doing this kind of thing. Of course, it
> > depends strongly on how intertwined the build of the front-end vs lib
> > is.
>
> I'm fairly sure that the X11 deps of openexr and libdjvulibre are both
> dependencies only for the frontends, not the libraries. If this was not
> the case then imagemagick-nox depending on these libraries would cause
> imagemagick-nox to have a transitive dependency on X11!
Concurred for openexr. Only need x11 for fltk-x11 which is only needed
for bin/exrdisplay. Looks like openexr (the set of front-end tools and
end-user docs) could easily be separated from openexr-dev (the
library) into independent .info files. Or just bin/exrdisplay could be
extricated into a separate .info (but seems simpler to keep the same
package-names containing the same things they do at present).
And also djvulibre appears similar in terms of dependencies, though I
didn't look at the build to see how hard it would be to move the libs
to a separate .info (djvulibre vs libdjvulibreXX-{dev,shlibs}).
Note that work is on-going to avoid propagating needless dependencies,
so even if there are linkages libA->libB and libB->libC, there may not
be libA->libC or need for libA to have any direct deps on libc*.
dan
--
Daniel Macks
[email protected]
http://www.netspace.org/~dmacks
------------------------------------------------------------------------------
_______________________________________________
Fink-devel mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.devel
