[Rpm-maint] idea for new keyword: ObsoleteBy

Stanislav Brabec sbrabec at suse.cz
Thu Sep 3 13:25:47 UTC 2009

Suppose that you have a custom package gimp-unstable-2.7, that is not
known to your vendor system. You want to follow updates, but once
gimp-2.8 appears, you want your package silently replace by a stable
distro package.

Or suppose that you created libfoo-mybranch-2.3, that contains an
important feature. You know, that your feature is implemented in
upstream version 2.4 and your libfoo-mybranch should be replaced by
libfoo then.

I think that for these purposes it would be nice to have reverse
Obsoletes - package {this_package} tells, that once package defined by
ObsoleteBy appears, solver will behave like if "Obsoletes:
{this_package}" is placed into it.

Version:    2.7.1
Provides:   gimp = %{version}
ObsoleteBy: gimp >= 2.7.1

Version:    2.3
Provides:   libfoo = %{version}
ObsoleteBy: libfoo >= 2.4

What do you think about such feature?

Best Regards / S pozdravem,

Stanislav Brabec
software developer
SUSE LINUX, s. r. o.                          e-mail: sbrabec at suse.cz
Lihovarská 1060/12           tel: +420 284 028 966, +49 911 740538747
190 00 Praha 9                                  fax: +420 284 028 951
Czech Republic                                    http://www.suse.cz/

More information about the Rpm-maint mailing list