Peter O'Gorman wrote:[]
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?!
glib and glib2 are not good examples; they are compatible. But there are many *-dev packages that conflict with and replace other *-dev packages and are to be freely swapped in and out during package building. If any other package had a Depends on one of them, it could not be swapped out.
This is a hard technical reason for forbidding Depends on some *-dev packages which have therefore the BuildDependsOnly flag set.
Policy comes into play when it is required that *all* packages containing header files should fall into this category. There are good reasons for this policy, but it is not complete; besides the BuildDependsOnly and BuildConflicts fields, it would need some replacement for the forbidden Depends, such as the InheritedBuildDepends that has been suggested but not yet implemented.
-- Martin
------------------------------------------------------- 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
