On Mon, 2008-01-07 at 16:15 +0100, Patrice Dumas wrote: > On Mon, Jan 07, 2008 at 10:40:05AM -0200, Eduardo M KALINOWSKI wrote: > > Hi, > > > > I'm attempting to package a program I wrote, that uses the GTK+ > > libraries. It uses features first found in the 2.10.X series, so I > > include > > > > BuildRequires: gtk2-devel >= 2.10.0 > > > > (and similar lines for glib and other required libraries). All this is > > OK. The problem is regarding the Requires for the generated .rpm. I > > could use > > > > Requires: gtk2 >= 2.10.0 > > > > but apparently this is bad style and bad for maintenance, because > > dependencies are found automatically on build time. However, without > > manually adding the requires, the generated .rpm contains (with regard > > to GTK+) this: > > > > libgtk-x11-2.0.so.0 > > > > that is, no mention of the version, and I expect that even a GTK+ 2.8 > > package (old as that may be) should provide that file with that name. > > > > What is the best way to handle that? Include the Require manually? > > Leave this as-is? > > I'd say the reverse than Rex, include the Require manually. But I may > well be wrong. Well, you are. If an upstream has its package properly designed (Esp. uses SONAMEs properly), then there should not be any need to let a run-time/application-package explicitly require a package by name. Ralf -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
