Skip to content

Systemd Bootstrap Complexity #261795

@blitz

Description

@blitz

Describe the bug

systemd depends on libraries (e.g. libfido2) which in turn depend on systemd. This cycle is currently broken by using systemdMinimal, a systemd version with all optional dependencies disabled. This has these problems:

  • people have to manually opt-in to systemdMinimal when they need udev or libsystemd or risk a dependency cycle
  • people misuse systemdMinimal to get a minimal systemd (which it is not really intended)
  • everyone gets two copies of systemd binaries and libraries in their system closure wasting 10-15 MiB.

@RaitoBezarius suggested that this could use a real bootstrap flow. Another solution would be to split building systemd libraries into a separate derivation. One wrinkle here is that libsystemd.so seems to hardcode the systemd bin/ path...

Notify maintainers

@RaitoBezarius @flokli @Mic92 @kloenk

Metadata

Metadata

Assignees

No one assigned

    Labels

    0.kind: bugSomething is broken6.topic: closure sizeThe final size of a derivation, including its dependencies6.topic: systemdSoftware suite that provides an array of system components for Linux operating systems.
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions