F24 System Wide Change: Systemd package split

[Zbigniew Jędrzejewski-Szmek]

On Thu, Nov 19, 2015 at 09:01:35AM +0100, Petr Spacek wrote:
> On 19.11.2015 08:52, Neal Gompa wrote:
> > On Thu, Nov 19, 2015 at 1:06 AM, Jan Kurik <jkurik at redhat.com> wrote:
> > 
> >> On Wed, Nov 18, 2015 at 9:07 PM, Brian C. Lane <bcl at redhat.com> wrote:
> >>> On Wed, Nov 18, 2015 at 05:32:02PM +0100, Jan Kurik wrote:
> >>>> = Proposed System Wide Change: Systemd package split =
> >>>> https://fedoraproject.org/wiki/Changes/systemd_package_split
> >>>>
> >>>> Change owner(s):
> >>>> Zbigniew Jędrzejewski-Szmek <zbyszek AT in DOT waw DOT pl>
> >>>>
> >>>> Two new subpackages will be split out from the main systemd package.
> >>>> systemd-container will contain stuff for launching and managing VMs
> >>>> and containers. system-udev will contain udevd and other
> >>>> hardware-related bits.
> >>>>
> >>>> == Detailed Description ==
> >>>> * systemd-container.rpm will consist of systemd-nspawn,
> >>>> systemd-machined, machinectl, systemd-importd, systemd-pull.
> >>>> * systemd-udev.rpm will consist of systemd-udevd, udevadm, udev rules,
> >>>> and the hardware database.
> >>>>
> >>>> Both new subpackages will be optional. systemd-container.rpm is useful
> >>>> only for people creating containers or VMs. systemd-udev.rpm should be
> >>>> generally installed, but can be skipped in containers.
> >>>
> >>> Thanks for the heads up, note that systemd-machineid is used by Anaconda
> >>> for live installs, and systemd-detect-virt is used to select a package
> >>> group when installing (non-live) to a VM.
> >>
> >> Forwarding the above to the devel@ list.
> >>
> >>> --
> >>> Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA
> >> (PST8PDT)
> >>
> >>
> > ​Why not also split out the systemd-network stuff? On most of our spins for
> > Fedora releases, we don't even use it. The only product that does is Fedora
> > Cloud (and maybe Fedora Atomic, too). It may not necessarily be a big chunk
> > of code (I don't know for sure), but I think it would be appreciated if it
> > was split out so that it's possible to reduce the amount of code that is
> > installed in a minimal context and to give developers/administrators a
> > better handle on what is installed on the system for security and auditing
> > purposes. ​
> 
> +1

networkd+resolved is about 1MB, and more importantly, they do not
bring in extra dependencies. We discussed also splitting that out on
the upstream mailing list, but in the end the gain didn't seem important
enough.

Zbyszek