Mailinglist Archive: opensuse-packaging (139 mails)

< Previous Next >
Re: [opensuse-packaging] Re: commit mozilla-nspr
  • From: Richard Guenther <rguenther@xxxxxxx>
  • Date: Thu, 27 Mar 2008 10:41:09 +0100 (CET)
  • Message-id: <Pine.LNX.4.64.0803271038590.4133@xxxxxxxxxxxxxx>
On Wed, 26 Mar 2008, Wolfgang Rosenauer wrote:

Hi,

h_root wrote:

+- Split out a shared library subpackage.

+Source1: README.SuSE
Patch1: prdtoa.patch
Patch3: pkgconfig.patch
BuildRoot: %{_tmppath}/%{name}-%{version}-build
+Requires: libnspr4 = %{version}

%description
NSPR provides platform independence for non-GUI operating system
@@ -52,8 +56,26 @@
--------
Mozilla Foundation <drivers@xxxxxxxxxxx>

+%package -n libnspr4
+Summary: Netscape Portable Runtime
+Group: System/Libraries
+Requires: %{name} >= %{version}

I'm wondering about that "split".

I understand and support the shared library policy for most cases but I don't
support it in this case.

The package now consists of
mozilla-nspr
libnspr4
subpackages where mozilla-nspr only contains README.SuSE (which I have yet to
see) and libnspr4 which contains three shared libraries with different names
and without SO-versioning.

The libraries seem to be versioned using a suffix in the name. But
the mozilla-nspr package should be dropped and ...

If it's really mandatory that the package name is libnspr4 (while libnspr4.so
is only one of the three libs) then please just do a package rename.

... as it is this should indeed have been a simple package rename. Also
the name is confusing (it isn't a proper shlib package), so
mozilla-nspr4 would have been my choice (if the goal is to be able to
install mozilla-nspr5 or whatever version in parallel).

Richard.

--
Richard Guenther <rguenther@xxxxxxx>
Novell / SUSE Labs
SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References