On Fri, Jul 15, 2005 at 10:44:04PM +0900, Junichi Uekawa wrote: > Stephen's points are valid and quite useful > considering an upstream developer's point of view, > but for random user joe who is trying to find a development > package, one of the following may help him find the right package > > > 1. creating a system-wide list of what -dev package does what. > > -> centrally requires work. Already started in d-shlibs. > > 2. creating a devlibs file which points to what shared library > is handled by which -dev package. > > -> requires manual intervention by all developers, > and utilizes an i-node for all shared library installations. > > 3. creating a package policy to Provides: a symbollic name > that can be traced from the shared library package name or > the shared library soname. > > -> non-invasive if it's done gradually.
Make shared library packages Suggest: their corresponding -dev packages. Regards, Daniel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
