On Sat, Jun 02, 2007 at 04:58:44PM +0900, Charles Plessy wrote: > I am a bit confused by the libraries which exist in -xpm and -noxpm > flavors. Are there cases where it is recommended not to use the -xpm > one? Or should we build-depend on foo-xpm | foo-noxpm? Is it necessary > to strictly depend on the -noxpm one if it seems that the program does > not interact with xpm files?
In terms of build-dependencies, you should really build-depend on one or the other; it's undesirable to have packages that randomly build with different feature sets as a side effect of having the non-preferred -dev package installed. If you're really certain that your package won't be interacting with xpm files (I guess it's not a general-purpose image processor, in that case?), build-depending on libgd2-noxpm-dev should be fine. In general I favor libgd2-xpm-dev just because I think the -noxpm stuff is pointless, but it's equally pointless to link against libraries you know you won't use. :) Anyway, building against libgd2-noxpm-dev will get you a proper dependency that will be satisfied by either the xpm or the noxpm version of libgd. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
