[opensuse-packaging] Another shared library policy doubt: renaming the source package.
At "Hints" the policy says: "There is no need to have a binary package that matches the source package name. In fact, you should avoid renaming the source package for different versions as we prefer to only have a single package version in the source repository." Thinking about this, isn't better to rename the source package? a) Renaming the package allows to have multiple versions in the source repository... but you are still free to have only one, whatever the name is. b) There isn't too much flexibility at naming the debug packages, the name always is <source_package_name>-debug*. Renaming also the source package you allow the debug packages of two library versions with different sonames to be also installed at the same time. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Wed, 27 May 2009, Cristian Morales Vega wrote:
At "Hints" the policy says: "There is no need to have a binary package that matches the source package name. In fact, you should avoid renaming the source package for different versions as we prefer to only have a single package version in the source repository."
Thinking about this, isn't better to rename the source package? a) Renaming the package allows to have multiple versions in the source repository... but you are still free to have only one, whatever the name is.
True, but usually this is not the case.
b) There isn't too much flexibility at naming the debug packages, the name always is <source_package_name>-debug*. Renaming also the source package you allow the debug packages of two library versions with different sonames to be also installed at the same time.
The proper fix for this is to create separate debuginfo packages for each shared library package, not renaming the source package. Richard. -- Richard Guenther <rguenther@suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
2009/5/27 Richard Guenther <rguenther@suse.de>:
On Wed, 27 May 2009, Cristian Morales Vega wrote:
b) There isn't too much flexibility at naming the debug packages, the name always is <source_package_name>-debug*. Renaming also the source package you allow the debug packages of two library versions with different sonames to be also installed at the same time.
The proper fix for this is to create separate debuginfo packages for each shared library package, not renaming the source package.
What do you mean with "create separate debuginfo packages"? I create a debug package through the "%debug_package" macro... that selects the name without asking: %debug_package \ %global __debug_package 1\ %package debuginfo\ ... You mean creating the debug packages without using the macro? That has the problem that it forces the packager to follow the changes in the macro (in < 11.0 only -debuginfo packages were created, now there are -debuginfo and -debugsource, tomorrow...). -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Wed, 27 May 2009, Cristian Morales Vega wrote:
2009/5/27 Richard Guenther <rguenther@suse.de>:
On Wed, 27 May 2009, Cristian Morales Vega wrote:
b) There isn't too much flexibility at naming the debug packages, the name always is <source_package_name>-debug*. Renaming also the source package you allow the debug packages of two library versions with different sonames to be also installed at the same time.
The proper fix for this is to create separate debuginfo packages for each shared library package, not renaming the source package.
What do you mean with "create separate debuginfo packages"? I create a debug package through the "%debug_package" macro... that selects the name without asking:
%debug_package \ %global __debug_package 1\ %package debuginfo\ ...
You mean creating the debug packages without using the macro? That has the problem that it forces the packager to follow the changes in the macro (in < 11.0 only -debuginfo packages were created, now there are -debuginfo and -debugsource, tomorrow...).
I know the deficiencies of the current system ;) That doesn't mean it is not fixable - in particular I think rpm itself should get support for creating debug packages (the issue seems to be that rpm does not support being notified late about packages to create). Richard. -- Richard Guenther <rguenther@suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - AG Nuernberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (2)
-
Cristian Morales Vega -
Richard Guenther