#143910 soname problems: sfs-lib package name without soname

Package:
sfftw2
Source:
fftw
Description:
library for computing Fast Fourier Transforms
Submitter:
Junichi Uekawa
Date:
2005-07-18 03:12:24 UTC
Severity:
wishlist
#143910#5
Date:
2002-04-21 16:35:52 UTC
From:
To:
Please fix the package name so that it complies with policy, after woody, possibly:
  libsfftw2


regards,
	junichi
#143910#10
Date:
2002-04-21 17:21:40 UTC
From:
To:
There is no such policy. Here's the relevant section of policy:

2.3.1. The package name
-----------------------

     Every package must have a name that's unique within the Debian
     archive.

     Package names must consist of lower case letters (`a-z'), digits
     (`0-9'), plus (`+') and minus (`-') signs, and periods (`.').  They
     must be at least two characters long and must contain at least one
     letter.

     The package name is part of the file name of the `.deb' file and is
     included in the control field information.

I hope you are not misreading the example in section 9 as stating
that packages containing shared libraries should be named after the
library. It simply states that libraries should be installed using
their normal name. Two different things.

The usual practice is to use the upstream name for the name of the
package (often appending the major version number for libraries).

Closing the bug.
#143910#15
Date:
2002-04-21 17:21:40 UTC
From:
To:
There is no such policy. Here's the relevant section of policy:

2.3.1. The package name
-----------------------

     Every package must have a name that's unique within the Debian
     archive.

     Package names must consist of lower case letters (`a-z'), digits
     (`0-9'), plus (`+') and minus (`-') signs, and periods (`.').  They
     must be at least two characters long and must contain at least one
     letter.

     The package name is part of the file name of the `.deb' file and is
     included in the control field information.

I hope you are not misreading the example in section 9 as stating
that packages containing shared libraries should be named after the
library. It simply states that libraries should be installed using
their normal name. Two different things.

The usual practice is to use the upstream name for the name of the
package (often appending the major version number for libraries).

Closing the bug.
#143910#20
Date:
2002-04-21 17:32:51 UTC
From:
To:
reopen 143910
thanks

That is not the usual practice.
And the "major number" is not appended after the library name...


11.2. Libraries
---------------

     All libraries must have a shared version in the `lib*' package and a
     static version in the `lib*-dev' package.  The shared version must be
     compiled with `-fPIC', and the static version must not be.  In other
     words, each `*.c' file will need to be compiled twice.



regards,
	junichi
#143910#25
Date:
2002-04-21 17:37:02 UTC
From:
To:
On Sun, 21 Apr 2002 13:21:40 -0400 "James A. Treacy" <treacy@debian.org> wrote:

You seem to be quite confident regarding policy in shared libraries,
would you mind to proofread my document :
http://www.netfort.gr.jp/~dancer/column/libpkg-guide/
#143910#32
Date:
2002-04-21 22:47:22 UTC
From:
To:
Bah humbug. Closing it again.
It just so happens that many upstream libraries contain the word lib in
the name. Thus many shared lib packages begin with that word. Also,
many developers like having lib packages begin with that word. Thus,
a lot use that convention. Common practice does not make it policy.
Also note that some common library packages do not begin with 'lib'
(for example, X Windows).

Look through a list of library packages and you'll notice that a lot
of them do end in a number. There is a very good reason for this: if
upstream bumps the major number of the library it is possible to install
both the old and the new version of the library. This is impossible
without the extra number. Having both versions in the distribution at
the same time makes upgrading much easier.

This section is about how .c files are compiled. Don't read more than
that into it. The use of 'lib*' and 'lib*-dev' is simply to
differentiate between the shared lib package and the one containing the
headers.
#143910#37
Date:
2002-04-22 04:05:23 UTC
From:
To:
reopen 143910
severity 143910 wishlist
retitle 143910 please rename the shared libraries when you feel fit, after woody

thanks

The bug exists, nothing has been fixed.  Please do not close it without
fixing anything. It just adds to my load.

Wrong. That is not exacly the case.

That is a bad example to play with.

Yes I know, and not just "lot of them", all of them should end in a number,
according to policy.

Yes. The soname of the library.
That you can complain to debian-policy, but it is a good convention
to have it that way.


For example, I have a script that automates this checking:

$ libinfodump.sh /usr/lib/libgthread.so
Package: libgthread-1.2-0
Section: libs
Depends: ${shlibs:Depends}

Package: libgthread-1.2-0-dev
Section: devel
Depends: libpthread0-dev,libc6-dev




I've put it up along with libpkg-guide.

regards,
	junichi