Richard Guenther
The library packaging policy forces you to rename curl-devel to either libcurl-devel or libcurl4-devel if you want to support development with different curl versions. We choose not to and rename it to libcurl-devel which will depend on libcurl4 for this version.
For the renaming you need a proper Provides: curl-devel and Obsoletes: curl-devel dependency for update to work. The split off of libcurl4 does not require anything special as shared lib requirements will take care of what is necessary.
Ok, some question on this, as I am currently working on the openssl split/rename: It is stated in http://en.opensuse.org/Package_Dependencies in the section "Renaming a package", that the old package name in the Provides tag should be versioned. The example given is: Name: package Version: 1.1 Requires: Provides: pac = 1.0 Obsoletes: pac <= 1.0 Conflicts: Now, this seems to imply that the version should be that one of the old version (before the rename was done). The argument given is that a later re-renaming should be possible. Looking at the libcurl-devel subpackage: %package -n libcurl-devel Provides: curl-devel = %{version}-%{release} Obsoletes: curl-devel This will expand to the current version-release number and seems to contradict the way it is done in the above document. What is the correct way to version the old package name in the Provides tag? Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org