[opensuse-packaging] Forcing dash in library package name
In build.opensuse.org/home:jengelh:dev/gf2x, I have a new package gf2x, where I decided to call the shared library package "libgf2x-1" instead of "libgf2x1" for purposes of clarity. Do Factory maintainers concur with this stance? If so, the shlib-policy check of rpmlint may need to be relaxed to allow the extra dash when $pkgname =~ /\d\w$/ (I don't see it yet necessary for \d\w+). libgf2x-1.x86_64: E: shlib-policy-name-error (Badness: 10000) libgf2x1 Your package contains a single shared library but is not named after its SONAME. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Do 15 Sep 2011 16:13:19 CEST Jan Engelhardt <jengelh@medozas.de> wrote:
In build.opensuse.org/home:jengelh:dev/gf2x, I have a new package gf2x, where I decided to call the shared library package "libgf2x-1" instead of "libgf2x1" for purposes of clarity. Do Factory maintainers concur with this stance? If so, the shlib-policy check of rpmlint may need to be relaxed to allow the extra dash when $pkgname =~ /\d\w$/ (I don't see it yet necessary for \d\w+).
It's not only rpmlint that might be confused with an "additional" dash in your package name. Other scripts and maybe even packages might need adaption, too (and I'm sure we will miss some in the first run). The policy itself is clear: no dash between the name and the library version. So following your suggestion would need an adapted policy and work on many other places. With kind regards, Lars -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (2)
-
Jan Engelhardt -
Lars Vogdt