Mailinglist Archive: opensuse-packaging (139 mails)
| < Previous | Next > |
[opensuse-packaging] Some notes from your friendly autobuild team
- From: Marcus Rueckert <darix@xxxxxxxxx>
- Date: Fri, 7 Mar 2008 16:23:24 +0100
- Message-id: <20080307152324.GA24708@xxxxxxxxxxxxxxxxxxxxxxx>
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}
2. Renaming a package
Just a short not how the proper provides/obsoletes should look like in
the usual case -> [2]
with kind regards
darix
[1] http://en.opensuse.org/Packaging/Shared_Library_Packaging_Policy
[2] http://en.opensuse.org/Upgrade_Dependencies#Renaming_a_package
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
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}
2. Renaming a package
Just a short not how the proper provides/obsoletes should look like in
the usual case -> [2]
with kind regards
darix
[1] http://en.opensuse.org/Packaging/Shared_Library_Packaging_Policy
[2] http://en.opensuse.org/Upgrade_Dependencies#Renaming_a_package
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
| < Previous | Next > |