Peter O'Gorman wrote:
> | I'm sure there is a good reason for this, but that really sounds rather
> | backwards...
>
> Yes there is a good reason. Think for a second and you'll realize what it
> is.... Packages which are "Build Depends Only" can not depend on other,
> unrelated, packages.
> It is erfectly fine for them to depend on their own
> shared libraries etc, it is required, in fact. But if it were to depend on,
> for example glib2, then it would be impossible for another package to
> BuildDepend on glib without a BuildConflicts on gtk+2-dev etc,
Why?!
BuildDepends
pkgA ----------------> glib
/|\
Depends |
gtk+2-dev --------------/
The isn't anything inconsistent there.
There is the BuildDependsOnly stuff in the Policy Manual (not quite
clear on the reason for that; from reading Policy, it sounds like a
technical limitation in the package manager). And yes, since glib2 is no
doubt BuildDependsOnly: true, gtk+2-dev can't declare a Depends on it by
policy.
> Depends and BuildDepends are totally different things.
Really? Policy says otherwise. Policy says the only difference between
Depends and Build-Depends is that Build-Depends does not apply after the
build has finished. From that, it seems, at least at first glance (and
from experience with how Debian handles it) --- absent BuildDependsOnly
--- that you'd have gtk+2 Depends: on the extra header packages, and
it'd all work.
> Please put some thought into things before postingand accusing others of
> stupidity.
I have not accused anyone of stupidity.
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
