"Redefined Horizons" <[EMAIL PROTECTED]> wrote: > Here is my question. Can I create a custom Debian package for Library A that > satisfies the dependency requirements of Package A, but still keep the older > version of Library A required by my other programs?
Of course. Look for example at the GTK+ library. In both sarge and sid, you'll find GTK+ 1.2 and GTK+ 2 (packages libgtk*), as well as packages using GTK+ 1.2, and packages using GTK+ 2. > In essence, I want to create my own custom Debian Packages to avoid > conflicts in package dependencies. Is this plausible? Yes, dpkg allows you to express dependencies in a comfortable way. Besides the New Maintainer's Guide, which you've already found, you should really read the Debian Policy to get a better understanding of these things. HTH, -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
