On 20 May 2011 09:54, Athmane Madjoudj <athmanem@xxxxxxxxx> wrote: > Also you might find the following presentation useful: > > http://www.redhat.com/promo/summit/2010/presentations/summit/opensource-for-it-leaders/thurs/pwaterma-2-rpm/RPM-ifying-System-Configurations.pdf That's a very nice solution - it will probably work for lots of the configs needed. Unfortunately, sudo doesn't like symlinks [root@uktest-lnx02 etc]# ls -l /etc/sudoers* lrwxrwxrwx 1 root root 12 May 20 09:05 /etc/sudoers -> sudoers.company -r--r----- 1 root root 337 May 20 08:30 /etc/sudoers.company [root@uktest-lnx02 etc]# sudo -l sudo: /etc/sudoers is not a regular file sudo: no valid sudoers sources found, quitting [root@uktest-lnx02 etc]# To my mind the ideal solution would be: %files %config(forcereplace) %attr(440, root, root) /etc/sudoers But as the presentation points out, both sudo and sudo-config would then "own" /etc/sudoers. What is the problem with that, exactly btw? When a new version of sudo was installed, it would overwrite the modified one, presumably. %config(stealfilefromotherpackage) maybe...? :) Calum -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
