Hallo.
I saw many renames of packages in the last days. We follow shared
library packaging conventions, but this policy says nothing about
renaming of source package.
I think, that it would be a good practice to use the same name for both
devel and source package. It's more convenient and even simpler to do it
in the spec.
I propose to add following line to the Packaging/Shared Library
Packaging Policy:
"Source packages should in general omit $NUM as .src.rpm packages for
different library versions and should follow -devel package naming."
In practice it will bring more convenient .src.rpm naming and nicer spec
files and less number of renames and drops in the repositories.
Deprecated:
Name: libfoo_1_2_3
Version: 1.2.3
%define orig_name libfoo
Source: %{orig_name}-%{version}.tar.bz2
...
%files
...
%files -n %{orig_name}-devel
It produces:
libfoo_1_2_3-1.2.3.i586.rpm
libfoo-devel-1.2.3.i586.rpm
libfoo_1_2_3-1.2.3.src.rpm
Proposed:
Name: libfoo
Version: 1.2.3
Source: %{name}-%{version}.tar.bz2
...
%files -n libfoo_1_2_3
...
%files devel
It produces:
libfoo-1_2_3-1.2.3.i586.rpm
libfoo-devel-1.2.3.i586.rpm
libfoo-1.2.3.src.rpm
--
Best Regards / S pozdravem,
Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o. e-mail: [EMAIL PROTECTED]
Lihovarská 1060/12 tel: +420 284 028 966
190 00 Praha 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
