On Mon, Jun 11, 2001 at 03:40:29AM +0200, Andreas Bombe wrote:
> Package: debian-policy
> Version: 3.5.5.0
> Severity: wishlist
>
> Policy wants shared libraries to be in packages of names like libfoo6
> for a libfoo.so.6. However this becomes confusing if the library name
> ends in a number so that the soversion is separated with a hyphen from
> the library name.
>
> $ egrep '^Package: lib.*-[[:digit:]]*$' unstable-Packages
> Package: lib3ds-1.0-0
> Package: libasis-3.13p-1
> Package: libgnat-3.13p-1
> Package: libgtrans-mysql-3-23
> Package: libgtrans-postgresql-6-5-3
> Package: libid3-3.7-13
> Package: libmath3d-0.3-0
> Package: libnewt-utf8-0
> Package: libole2-0
> Package: libraw1394-5
>
> The last three are what I am talking about specifically (libraw1394 is
> mine, btw), generally this also applies to the version-in-name problems
> seen above (don't ask me wtf libgtrans is up to).
>
> To document this practice, I propose the policy patch:
>
> --- policy.sgml.orig Mon Jun 11 01:54:55 2001
> +++ policy.sgml Mon Jun 11 02:14:58 2001
> @@ -5547,6 +5547,12 @@
> </p>
> </footnote>
> and <tt><var>libraryname</var><var>soversion</var>-dev</tt>.
> + Alternatively, if it would be confusing to directly append
> + <var>soversion</var> to <var>libraryname</var> (e.g. because
> + <var>libraryname</var> itself ends in a number), you may use
> + <tt><var>libraryname</var>-<var>soversion</var></tt> and
> + <tt><var>libraryname</var>-<var>soversion</var>-dev</tt>
> + instead.
> </p>
Seconded. This seems eminently reasonable and current practice in the
examples you're referring to.
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London
Debian GNU/Linux Developer, see http://people.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
