[arch-dev-public] upgrade path for some config files?
a.radke at arcor.de
Wed Mar 24 21:47:07 CET 2010
The current cups package is missing some configuration files that I
want to introduce with a new minor bugfix release.
The cupsd has created probably some of these files already if needed but
I want to ship empty files from now on with correct permissions like
other major distributions do. This will also solve some bugs. I've put
the files into backup array for future upgrades.
But how should I handle the initial update. pacman -S cups shows
several file conflicts because the files in the system are not under
pacman control. Can a safe upgrade done by pacman without user
interaction? If not we should probably announce it in a news that users
will have to backup the conflicting files and will have to remerge their
configuration after the update.
see my commit for cups 1.4.2-4. I'll keep it in staging for now.
More information about the arch-dev-public