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.
OK, that makes sense. Well, they could be swapped out (by removing the depending packages), but I'm guessing that's not implemented.
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.
I'm rather curios why you'd want a IneheritedBuildDepends instead of just fixing the Depends handling --- because, currently, the installed gtk+2-dev is very much broken[0], and IneheritedBuildDepends (guessing from the name) won't fix that.
Is there a good pointer into the list archives?
[0] It, e.g., has #includes to pango, which will fail when only Essential and
Depends are installed. Not to mention pkg-config is very upset about it.
------------------------------------------------------- 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
