1 |
On Wed, Jul 10, 2019 at 11:02 PM William Hubbs <williamh@g.o> wrote: |
2 |
> |
3 |
> > RDEPEND="sysv-utils? ( !sys-apps/sysvinit ) |
4 |
> > !sysv-utils? ( sys-apps/sysvinit )" |
5 |
> |
6 |
> I like this, but the second branch (!sysv-utils) is not really needed, |
7 |
> because if we put sysvinit as the first RDEPEND of virtual/init, we |
8 |
> don't need to worry about installing it through rdepend in openrc. |
9 |
|
10 |
Does openrc actually work with all the stuff you have in your proposed |
11 |
virtual/init? |
12 |
|
13 |
For example, you have systemd in there. I'm pretty sure you can't use |
14 |
systemd as PID1 and then use openrc as your service manager. I mean, |
15 |
you probably could come up with some way to do that, but certainly |
16 |
openrc doesn't work that way today, or systemd for that matter. |
17 |
|
18 |
You have runit in there as well. Can you use runit as PID1 and openrc |
19 |
as your service manager? |
20 |
|
21 |
If the only init implementations that openrc actually works with are |
22 |
sysvinit and its own init, then I'd just do it the systemd way. The |
23 |
init virtual only adds value insofar as these other packages actually |
24 |
provide an init that any other service manager could actually use. |
25 |
|
26 |
If openrc works with busybox init/etc I could see an argument for |
27 |
maybe having a virtual that can pull in either, though in that case it |
28 |
might make sense to use that in systemd as well. |
29 |
|
30 |
> We |
31 |
> can also add sys-apps/openrc as an rdepend of sys-apps/sysvinit |
32 |
> possibly. I'll take a look at that. |
33 |
|
34 |
I think it makes more sense to have a service manager pull in a |
35 |
compatible PID1 rather than the reverse. For example, systemd can |
36 |
pull in sysvinit for access to shutdown/telinit/etc but it makes no |
37 |
sense in that case to force openrc to get installed. You could even |
38 |
use sysvinit without any other service manager. |
39 |
|
40 |
-- |
41 |
Rich |