[Pkg-sysvinit-devel] Bug#887266: initscripts should depend on e2fsprogs explicitly

Helmut Grohne helmut at subdivi.de
Mon Jan 15 14:43:19 UTC 2018


On Mon, Jan 15, 2018 at 02:35:01AM +0100, Adam Borowski wrote:
> This is an interesting case.

Indeed.

> Small containers, systems and chroots that need an init really want to use
> sysvinit (thus initscripts) instead of systemd, as it's drastically smaller,
> both in terms of memory use and disk size.  Thus, they're what needs removal
> of e2fsprogs the most -- ie, adding the dependency wouldn't be the right
> thing to do.

Correct.

> As you have researched relationship between minimal install packages, you
> likely know more than me.  Thus, could you advise?

I'm sorry. I tend to ignore sysvinit nowadays. My approach here would be
to add the dependency as that is no regression: initscripts currently
(implicitly) depends on e2fsprogs and it keeps doing so.

Then as a secondary step, I'd leave it to people to actually remove the
dependency by refactoring either initscripts or e2fsprogs.

Of course if both systemd and sysvinit end up pulling e2fsprogs, we'll
not win much. But we know precisely where to look then.

Helmut



More information about the Pkg-sysvinit-devel mailing list