rpm4/rpm5 incompat: rpm5 firing on provides

[Elan Ruusamäe]

On 30.10.2012 18:04, Jeffrey Johnson wrote:
> On Oct 30, 2012, at 11:48 AM, Elan Ruusamäe wrote:
>
>> >On 30.10.2012 17:42, Jeffrey Johnson wrote:
>>> >>Its rather unusual to expect
>>> >>a script to run after all package contents -- including
>>> >>the trigger script -- have been removed.
>> >the trigger is to migrate config files from "initscripts" package from redhat to pld "rc-scripts" package
>> >
> Duplicating what scripts one expects, and marking with %config so no
> local modifications are lost, and then
> 	Obsoletes: initscripts < X.Y.Z
> 	Conflicts: initscripts < X.Y.Z
> 	Provides: initscripts = X.Y.Z
> is the "standard" way that a package renaming from "ini scripts" -> "rc-files" is achieved.
can't mark by version, because they (redhat/fedora) increase the version 
as well (it's foreign package, not under pld control)

the files are still compatible with pld initscripts, so no reason to 
limit migration from redhat 6.2 only.
> Note no trigger needed and that %config is used (which cannot be achieved through
> scripting because there is no ability to track %confoig file states into an rpmdb).
>
>> >so if "initscript" package is removed (replaced by rc-scripts), trigger locates interface configs to directory "rc-scripts" expects
>> >
> Is the directory renaming really necessary?
hell knows, it's been renamed since '99 :)


-- 
glen