On Tue, 2011-05-24 at 13:50 +0100, Tejas Guruswamy wrote:
On 24/05/11 13:31, Atri wrote:
If someone could tell me if it possible for the -devel package depending on a single shlib package to have a different name instead of following the shlib package name closely, without getting rpmlint to throw warnings, it would be a big help.
Thanks, and bye
-- Atri
[1] https://build.opensuse.org/package/show?package=plplot&project=home:badshah400 [2] http://en.opensuse.org/openSUSE:Shared_library_packaging_policy
If the libraries within the package are 1) tightly bound to the main program version, i.e. they release in lock-step and won't work unless versions match 2) not going to be used by any other package without having the main program as well then it should fall under the exceptions to the SLPP and you should package them within the main package (because then they aren't true shared libraries, they ideally could be packaged as modules and not installed in /usr/lib* but instead in /usr/lib/%{name} -- but that's an issue to raise with upstream)
From what I would guess about your application, this is probably the case, so it's probably sufficient to have a binary package (or maybe split by frontend -qt -gtk or whatever) with a single -devel package. Easier than struggling with hundreds of packages with crazy names that would always have to be installed & removed together.
Regards, Tejas
Thanks Tejas. I was splitting up the various packages because it would mean less download over the internet for a user. I mean not everyone would need the tcl, wxwidgets and qt bindings so they could just leave them off. Don't you think this is the right thing to do? -- Atri -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org