On Wed, Feb 01, 2023 at 09:16:52PM +0100, Helmut Grohne wrote: > > (The `--include=init` option should also be avoided for custom images.) > > I distill that this is the actual request and retitle the bug > accordingly.
This is less obvious than it initially seems, so I'm also requesting feedback from Johannes and Jochen as to where we should head. We currently --include=init, but we really expect it to be systemd. So that's a lie already. Should we change --include=init to --include=systemd-sysv? + We'd stop pretending things would just work with sysvinit. + We'd install one less package. - That'd break --skip=systemdnetwork -- --include=sysvinit-core, but then you could --skip=systemd -- --include=sysvinit-core. Then we're into adding a skip option. I'd call it "initsystem" or "systemd" depending on the previous answer. Should --skip=systemd imply --skip=systemdnetwork? + When not skipping them, it'd pull in systemd (not systemd-sysv) anyway. - Skip implications cannot be unskipped. Should --skip=systemd imply --skip=autologin? + autologin would not work without systemd. - A user could provide a custom systemd from source and that might work. - Skip implications cannot be unskipped. At this time, I slightly prefer --include=sysvinit-core and skip implications, but I'd also like to hear your opinions to find something intuitive. Don't hesitate to add short, opinionated replies. Helmut
