[aur-general] [arch-dev-public] [REMINDER] systemd conversion

David J. Haines djhaines at gmx.com
Thu Oct 4 15:24:36 EDT 2012

On Thu, Oct 04, 2012 at 09:19:00PM +0200, Tom Gundersen wrote:
> On Thu, Oct 4, 2012 at 9:12 PM, David J. Haines <djhaines at gmx.com> wrote:
> > Is there now any equivalent to .pacnew files for what would have been
> > configuration files in /etc/conf.d? That is to say, if before a user
> > edited /etc/conf.d/<some file> and that file received a newer version in
> > its package, a .pacnew file would be left behind, indicating that the
> > user should set about merging his/her custom configuration into the
> > newer "stock" configuration. Very useful, that. Now, however, it would
> > seem that the user will never see such a message (even though
> > potentially critical changes have been made to the unit file) because
> > the custom unit file in /etc/systemd/... won't be tracked by pacman.
> >
> > Is there a good solution for detecting such changes, so that users can
> > once again merge their necessary changes into the systemd equivalents of
> > /etc/conf.d files?
> Using Includes rather than copying the full service file reduces this
> problem somewhat. Moreover, there is the systemd-delta tool which is
> quite useful (it shows you the "diff" between the shipped service file
> and the actual one that you are using).
> -t

Nice. Thanks!
David J. Haines
djhaines at gmx.com

More information about the aur-general mailing list