Re: systemd as external dependency

[Lennart Poettering <mztabzr 0pointer de>]

On Wed, 18.05.11 17:51, Federico Mena Quintero (federico ximian com) wrote:

> 
> On Wed, 2011-05-18 at 21:50 +0100, Bastien Nocera wrote:
> 
> > Which is why I've asked Lennart to add a flag to systemd's configure to
> > install only the little servicey bits, for Linux distros, and the docs
> > would serve as basis for implementation of other OSes.
> 
> That's fine.  I still think other distros/systems may be feel it to be a
> little onerous to have to download a "big system-level package" (even if
> it's just perception) to install random services like that.
> 
> (Maybe a "system-services" tarball, if you really don't like the name of
> AdminKit?) :)

I definitely don't want to split this off. It's systemd on both sides
here, writing and reading the configuration files. For example, for the
locale settings mechanism we need to apply changes to disk which are
read by systemd on the next boot, and we also need to apply them to the
running instance. If we maintain this together it is easy to ensure that
this stays in sync. 

Also the hostnamed code actually shares substantial code with the rest
of systemd (like file parsers, dbus glue, logging, utilities, ...). I
don't want to duplicate that in another project having to sync things
boths way all the time.

My plan with systemd is to clean up the mess that we traditionally had
with a chaotic collection of basic mix and match building blocks. I want
to work against that, and hence splitting these things off is
diametrically opposed to my goals.

I am also a very lazy person. I maintain way too many packages of our
stack already. I am pretty sure I don't want to add another to that.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.