On Mon, 14.05.12 14:51, Dave Reisner ([email protected]) wrote: > > On Mon, May 14, 2012 at 08:39:23PM +0200, Lennart Poettering wrote: > > On Thu, 10.05.12 23:27, Seblu ([email protected]) wrote: > > > > > Hello, > > > > > > on my archlinux test computer i would have first console not cleaned > > > and other spawned statically (crazy idea isn't it). > > > > > > So I've turned NAutoVTs to 1 in /etc/systemd/systemd-logind.conf. > > > I've copied /usr/lib/systemd/system/[email protected] into > > > /etc/systemd/system/ and patched as following: > > > > > My issue is at every systemd package upgrade, [email protected] is > > > replaced by a new one linked to > > > /usr/lib/systemd/system/[email protected]. > > > And i loose my configuration. > > > > This sounds like a packaging problem downstream, nothing we can fix > > upstream. > > > > Strange that you say that, since make install does the following: > > ( cd $(DESTDIR)$(pkgsysconfdir)/system/getty.target.wants && \ > rm -f [email protected] && \ > $(LN_S) $(systemunitdir)/[email protected] [email protected] ) > > See line 3128ish on git master. This is absolutely something that we (Arch > Linux) inherit from upstream.
"make install" is not really too useful for end-user installs, is it? The distro package manager should handle configuration files specially, the way .rpm or .deb do it. This is not a problem exclusive to systenmd. All automake based packages overwrite configuration files on "make install", and expect the package manager to handle this more nicely if the simple an brutal scheme is not sufficient... Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
