1 |
All, |
2 |
|
3 |
This bug [1] brings up an issue that I would like thoughts about. |
4 |
|
5 |
sys-fs/udev and net-wireless/bluez, among other packages, install udev |
6 |
rules which assume that you are using openrc. |
7 |
|
8 |
On systems where openrc is not used in the boot process, this causes |
9 |
issues because openrc services are run by the udev rules even though |
10 |
openrc did not boot the system. |
11 |
|
12 |
The author of the bug feels that the way to fix this is for us to put a |
13 |
check in openrc that makes it refuse to run services if it was not used |
14 |
in the boot process. |
15 |
|
16 |
This may work; however, I do not feel that it addresses the root cause |
17 |
of the bug. I feel that the root cause is packages unconditionally |
18 |
installing udev rules which assume everyone uses openrc. |
19 |
|
20 |
My proposal is to give these packages an "openrc" use flag which will |
21 |
control whether or not openrc specific support will be installed. This |
22 |
would be on by default, of course, since most of us use openrc. |
23 |
|
24 |
The author of the bug is correct about the disadvantage of doing this -- |
25 |
if you want to switch on or off openrc support, this will require a |
26 |
rebuild of the affected packages. |
27 |
|
28 |
I feel that the advantage of this approach outweighs this disadvantage |
29 |
because this approach allows the user to tell udev not to even attempt |
30 |
to run openrc services, and this will lead to a more efficient system. |
31 |
|
32 |
Any input would be appreciated. |
33 |
|
34 |
William |
35 |
|
36 |
[1] http://bugs.gentoo.org/show_bug.cgi?id=364159 |