Bug 446138 – >=sys-apps/systemd-196 should optionally depend on sys-apps/kmod

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Sean McGovern 2012-12-05 19:00:18 UTC]

Previously this was a hard dependency but is now optional. Recommend adding a kmod USE flag to opt-in/out of new behaviour.

[Comment 1 Jeroen Roovers (RETIRED) 2012-12-05 19:16:00 UTC]

What is "this"?

[Comment 2 Michał Górny 2012-12-05 19:41:57 UTC]

(In reply to comment #0)
> Previously this was a hard dependency but is now optional. Recommend adding
> a kmod USE flag to opt-in/out of new behaviour.

Hmm, for people with monolithic kernels or does it have some use I'm unaware of?

There's also the case of its relationship to udev.

[Comment 3 Sean McGovern 2012-12-05 19:49:21 UTC]

Currently both sys-apps/systemd and sys-fs/udev pull in sys-apps/kmod but as of release 196, without a --{enable,disable}-kmod added to configure this setting is subject to the whims of the systemd developers.

It's better to make this explicit.

[Comment 4 Michał Górny 2012-12-05 19:52:41 UTC]

(In reply to comment #3)
> Currently both sys-apps/systemd and sys-fs/udev pull in sys-apps/kmod but as
> of release 196, without a --{enable,disable}-kmod added to configure this
> setting is subject to the whims of the systemd developers.
> 
> It's better to make this explicit.

I've noticed the flag but what are its implications? I'd make it explicit if I knew how to describe it. Does it only involve inability to load kernel modules?

[Comment 5 Sean McGovern 2012-12-05 20:01:22 UTC]

It enables/disables the ability for systemd to direct loading of kernel modules. Even with a non-monolithic kernel, there may be configurations where a user does not want systemd and/or udev to control that.

[Comment 6 Sean McGovern 2012-12-05 20:03:05 UTC]

This should default to enabled in order to not generate regressions for users upgrading from <196.

[Comment 7 Michał Górny 2012-12-05 22:32:34 UTC]

USE=kmod now in udev & systemd.