Mailinglist Archive: opensuse-packaging (139 mails)

[Richard Guenther <rguenther@xxxxxxx>]

On Fri, 7 Mar 2008, Marcus Rueckert wrote:

> hi,
>
> 1. good ways of doing library policy compatible packages
>
> Since quite some time we have some policy for packaging shared
> libraries. [1]
>
> We all had lots of fun and work with it already. There is some way to
> save some work for all of us. I will use libetpan as an example here.
>
> in the current factory package we have libetpan11 and libetpan-devel.
> and in the queue there is an update that would bump the soname to
> libetpan.so.13. now it would be renaming a package in autobuild, rename
> the spec, rename the changes file and check in the new package.
>
> To save us all a bit work we slightly change the packaging:
>
> we rename the package back to libetpan and let the spec generate an
> empty main package. Additionally we have 2 subpackages (libetpan13 and
> libetpan-devel).
>
> Of course you should add a provides to the libetpan13 package:
> Provides: %{name} = %{version}

No, certainly not.  shared library packages should not provide anything.

What reason for should this provide be?

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