On Sat, Apr 22, 2006 at 07:49:25PM -0600, Hubert Chan wrote: > reassign 359158 gnustep-base-common > thanks > > (Reassigning to gnustep-base-common, so that when libgnustep-base1.12 > goes in, this bug will still be current.) > > Hi Bill, > > On Sun, 26 Mar 2006 23:36:44 +0200, Bill Allombert said: > > > There is a circular dependency between libgnustep-base1.11 and > > gnustep-base-common: > > > libgnustep-base1.11 :Depends: gnustep-base-common (>= 1.11.2-2) > > gnustep-base-common :Depends: libgnustep-base1.11 (>= 1.11.2) > > Yes. As far as I know, GNUstep applications that link against > libgnustep-base* require the gdnc program (at least), which is in > gnustep-base-common. And of course gdnc is linked against > libgnustep-base, so gnustep-base-common must depend on libgnustep-base*. > > I'm thinking of making libgnustep-base* Recommends: gnustep-base-common > instead of Depends:. Does anyone know of any breakages that might > happen if I do that? Since aptitude is the suggested installer for > sarge onwards, and aptitude will pull in Recommends:, this should still > ensure that gnustep-base-common gets installed. > > (AFAIK, gnustep-gui will need similar treatment.) > > Bill, do you have any other possible suggestions?
Well I suppose libgnustep-base1.11 does not need gnustep-base-common, but rather the programs linked with libgnustep-base1.11 ? In that case you could remove the dependency and make sure packages linked with libgnustep-base1.11 depend on gnustep-base-common, maybe by adding gnustep-base-common to the shlibs file ? Cheers, Bill. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]