[systemd-devel] Have custom agetty behaviour even after upgadres

[Dave Reisner]

On Mon, May 14, 2012 at 11:01:53PM +0200, Lennart Poettering wrote:
> On Mon, 14.05.12 14:51, Dave Reisner (d at falconindy.com) wrote:
> 
> > 
> > On Mon, May 14, 2012 at 08:39:23PM +0200, Lennart Poettering wrote:
> > > On Thu, 10.05.12 23:27, Seblu (seblu at seblu.net) 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/getty at .service into
> > > > /etc/systemd/system/ and patched as following:
> > > 
> > > > My issue is at every systemd package upgrade, getty at tty1.service is
> > > > replaced by a new one linked to
> > > > /usr/lib/systemd/system/getty at .service.
> > > > 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 getty at tty1.service && \
> >     $(LN_S) $(systemunitdir)/getty at .service getty at tty1.service )
> > 
> > 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.

I'm saying 'make install' from within the packaging environment with
some sort of DESTDIR= variable pointing to the packaging root. Fedora
does this, Mageia does this, Arch does this. Anyone who tries to package
something this complex on their own is doing it wrong.

I'll bring this closer to home. Why does "make DESTDIR=%{buildroot} install"
write to $(sysconfdir) when you've always proclaimed that it's admin territory?
Why not write this link as: $(systemunitdir)/getty.target.wants/getty at tty1.service?

d


> 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
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel