On Mon, Feb 19, 2007 at 12:33:54PM -0500, Bill Nottingham wrote: > Axel Thimm (Axel.Thimm@xxxxxxxxxx) said: > > > No. If it changes from %config (modified) to non-%config, it would > > > still get moved on upgrade, unless I'm forgetting the state machine. > > > > That's why I suggested %prein > > I think we're talking past each other. AFAIK, it will get successfully > saved as .rpmsave *without* any %pre magic. Indeed, my issue is to have the upgrade do something with the existing configuration in some scripts, not simply archive away the user's config into an .rpmsave file. The upgrade would break on the user and leave him fiddle out where his config has vanished to. And the cleanest way is for the package to extract the config out of the script and place it to the new canonical place during the upgrade. Hopefully the config will be in some extractable form. Note: We are talking only about package that don't only tag init files as %config, but indeed misuse them to store config information. Not that I know of any to present an example, but Jesse said there are some. This has nothing to do with the tons of packages marking init files as %config even though all config has been moved to sysconfig ages ago. Perhaps it become clearer if we find such a package and discuss what we'd like an upgrade to perform. -- Axel.Thimm at ATrpms.net
Attachment:
pgpivuDKLW7nJ.pgp
Description: PGP signature
-- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
