On 06/12/2013 02:27 AM, Adam Williamson wrote:
On Mon, 2013-06-10 at 15:04 +0200, Michael Schwendt wrote:
Typically, one adds only the Obsoletes tag with a maximum version, so the
obsolete package may return with a higher version.
https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.2FReplacing_Existing_Packages
| If a package supersedes/replaces an existing package without being
| a compatible enough replacement as defined in above, use only the
| Obsoletes from above.
Just to reinforce: please, please do this; have something Obsolete: it.
It is absolutely not correct to just leave the package dangling with
dependencies that break upgrade processes and require users to remove it
manually. Anything that breaks the upgrade bug from release to release
is a bug.
Please just have something Obsolete: it. If you want to notify the user
of the change you can do any or all of the following:
* Include a README.cups-php or something in the %doc of the package
* Ask the documentation team to add a Release Note
* Have the package print out a message about the change on update (there
are 'standard'ish ways to do this, I don't know off the top of my head
if any or all of them are allowed/recommended practice in Fedora, but it
should probably be in the Guidelines somewhere). If you do this, try to
nail the logic such that everyone sees the message only once, at the
point when they do the update that actually does the Obsolete.
That does the trick. Thank you both !
--
Jiri
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
