[systemd-devel] [PATCH 2/2] sysusers.d: split files to cope with split packages.

Barbieri, Gustavo gustavo.barbieri at intel.com
Mon Oct 6 21:54:41 PDT 2014


> -----Original Message-----
> From: Lennart Poettering [mailto:lennart at poettering.net]
> Sent: Thursday, October 02, 2014 4:19 AM
> To: Barbieri, Gustavo
> Cc: Zbigniew Jędrzejewski-Szmek; systemd-devel at lists.freedesktop.org
> Subject: Re: [systemd-devel] [PATCH 2/2] sysusers.d: split files to
> cope with split packages.
> 
> On Tue, 30.09.14 14:44, Gustavo Sverzut Barbieri
> (gustavo.barbieri at intel.com) wrote:
> 
> > > systemd-timesyncd is ~400kb. Other binaries aren't too big
> > > either. Splitting everything up complicated things, and I'm not
> convinced
> > > that this is a useful change.
> >
> > indeed they are not big per se, but see my other email about
> tmpfiles,
> > they contribute to a misinterpretation of systemd. since they are
> > optional I want to make that clear and help the user to choose.
> >
> > I do have a complete set of packages for yocto that generates that
> > nicely and the final system size difference is huge: 7.5 to 30Mb
> > (whole system, not just systemd, but the dependencies, etc -- in
> > contrast sysvinit + busybox is 6.5Mb).
> >
> > as I wrote in the other email, I'll make sure that some packages
> are
> > highly recommended (ie: journal, udev, sysctl...), but forcing
> 
> We don't support builds without journal or udev. We simply don't.

I'm not trying to build without, just running without. Actually I'm not using any of --disable-SERVICE_OR_DAEMON, I build with all of them and let the user install or not the package -- thus the need for different *files* :-)

 
> > everyone to ship a ntp client (timesyncd) is asking for trouble
> when
> > people analyze systemd x options.
> 
> Yes, timesyncd should definitely be optional, and so should
> resolved,
> that's true. I'd be OK with splitting those out on
> tmpfiles/sysusers,
> but would really prefer this to be done via m4, rather than in
> seperate files.

As per above, I don't want to build without, rather build with all and just package them in separate. In the recommended setup users will get all they need. Just in cases where they remove (blacklist) the "systemd-services-essential" they can run without those (tmpfiles, sysusers...), I guess the name makes it clear they are not something to mess with if you are unsure.

Please help, this will be for good. The m4 macros just makes the build system and packaging more difficult. It would only be useful for systems like Gentoo.

BR,
-- Gustavo
(sorry the formatting, stupid outlook in this laptop)



More information about the systemd-devel mailing list