Re: [Fink-devel] pkgconfig policy

2003-08-29 Thread Chris Zubrzycki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, August 28, 2003, at 10:07 AM, Peter O'Gorman wrote: On Thursday, August 28, 2003, at 10:31 PM, Benjamin Reed wrote: Peter O'Gorman wrote: I don't see the need for this to be in a Recommends field, would it not be better in a Desc* type

Re: [Fink-devel] pkgconfig policy

2003-08-29 Thread David R. Morrison
What about fixing the fink dep engine, so that BuildDependsOnly packages may depend on other BuildDependsOnly, and then a kde packahe could BuildDepend on kdelibs3-dev and a few other -dev packages it needs, and fink will make sure everything needed is there; fink would need to

[Fink-devel] pkgconfig policy

2003-08-28 Thread David R. Morrison
Dear Fink developers, As some of you know, the pkgconfig system is being used extensively with GNOME2 packages and possibly with other systems as well. The pkgconfig system aims to solve the problem of multiple versions of a shared library by (1) carefully giving different names to different

Re: [Fink-devel] pkgconfig policy

2003-08-28 Thread David R. Morrison
Peter O'Gorman [EMAIL PROTECTED] wrote: Hi David, On Thursday, August 28, 2003, at 09:41 PM, David R. Morrison wrote: SHORT TERM SOLUTION: Although we should not allow a -dev splitoff to Depend on another -dev splitoff, we can use the Recommends field to specify the other -dev

Re: [Fink-devel] pkgconfig policy

2003-08-28 Thread Benjamin Reed
Peter O'Gorman wrote: Hi David, On Thursday, August 28, 2003, at 09:41 PM, David R. Morrison wrote: SHORT TERM SOLUTION: Although we should not allow a -dev splitoff to Depend on another -dev splitoff, we can use the Recommends field to specify the other -dev splitoffs which are relevant.

Re: [Fink-devel] pkgconfig policy

2003-08-28 Thread Peter O'Gorman
On Thursday, August 28, 2003, at 10:31 PM, Benjamin Reed wrote: Peter O'Gorman wrote: I don't see the need for this to be in a Recommends field, would it not be better in a Desc* type field, or simply as a #comment in the .info file? It's not a matter of need, but it does make sense to me. If