El sáb, 14-10-2006 a las 22:12 -0700, Steve Langasek escribió: > severity 391721 important > severity 391725 important > thanks > > On Sun, Oct 08, 2006 at 12:39:22PM +0200, Jose Carlos Garcia Sogo wrote: > > With latest Beagle uploade (version 0.2.10-2) I have splitted > > beagle-dev in two packages: the old beagle-dev will from now on only > > contain files needed for C#, while there is a new libbeagle-dev > > package for C stuff. > > > As I think you are only using C bindings, you should build depend on > > libbeagle-dev, and you will also benefit on not needing to install > > beagle to compile this package. > > On Sun, Oct 08, 2006 at 12:47:49PM +0200, Jose Carlos Garcia Sogo wrote: > > With latest upload of beagle (0.2.10-2) I have splitted beagle-dev in > > two packages: old beagle-dev will only contain files needed for C# > > development, while new libbeagle-dev will contain pieces needed for C > > development. As I think you are only using libbeagle, you should > > change your build dependencies to depend on libbeagle-dev. > > First, this version of beagle is still in NEW, so the severity is premature.
Well, it was not expected to be so long in NEW. > > Second, does the new beagle-dev not depend on libbeagle-dev? That would > solve any release-critical transition issues here anyway. There are only two packages with this problem: kerry and beaglefs. The idea is just not making libbeagle-dev dependant on beagle-dev, so it does not bring beagle itself. This way, people developing in C doesn't need even Mono installed. In a future, beagle C# libraries should be also splitted, so we end with: C Mono beagle (ui) beagled (daemon) libbeagle0 libbeagle-cil libbeagle-dev beagle-dev (or libbeagle-cil-dev) But with no dependency from C stack to C# one. Cheers, -- Jose Carlos Garcia Sogo [EMAIL PROTECTED]