On Thu, Nov 09, 2006 at 04:41:15PM +0530, R.Ramkumar wrote: > The current compat package pulls in c, c++, and perl dev packages of > graphicsmagick all at once. Not only are the sizes of the c/c++ > packages substantial, but they carry along a train of dev package > dependencies for the corresponding image libraries. It would be > great if you can split the perl and c/c++ compat packages to reduce > the number of dependencies.
Of course I've considered that when I first introduced the compat package, but I was also afraid of micropackaging tiny wrapper code that bloats the Packages file. Finally, I opted for a single blob containing all language bindings because it's intended to be used as a temporary band aid, eg. in Build-Depends, but not as a permanent solution. Typically, it shouldn't be installed unless you're doing porting work or building a depending package. So the large dependency chain should only be a temporary nuisance. At least, that was my reasoning when taking this choice, but of course you're very welcome to try and convince me otherwise. Regards, Daniel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
