1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 08/02/16 11:18 AM, Rich Freeman wrote: |
5 |
> However, I think we're actually missing the bigger issue here. |
6 |
> Why is this virtual even in @system to begin with? When I set up |
7 |
> a chroot or some kinds of containers I don't need udev, or |
8 |
> sysvinit (or openssh - but let's set that one aside for now). |
9 |
> |
10 |
> We don't stick grub or genkernel or even gentoo-sources in our |
11 |
> stage3s. Why stick (e)udev in there? |
12 |
> |
13 |
> It seems like this should just be another step in the handbook - |
14 |
> pick your desired device manager. |
15 |
> |
16 |
> Obviously if we produce a boot CD it will need a device manager |
17 |
> (and kernel and bootloader and network manager), and I don't care |
18 |
> which one it is. |
19 |
> |
20 |
> This just seems more like the Gentoo way, and it completely |
21 |
> sidesteps all the controversy over defaults. We're already |
22 |
> working on fixing the few remaining functions.sh references so |
23 |
> that openrc can be removed from the system set as well. |
24 |
> |
25 |
|
26 |
I thought the point of this discussion had to do mostly with what |
27 |
udev variant gets installed when a user doesn't specify one. And |
28 |
AFAIK, since there are still plenty of packages that *DEPEND on |
29 |
virtual/udev , the discussion's still worth having isn't it? |
30 |
|
31 |
Besides, if we just move the goal of this discussion from "order of |
32 |
atoms in virtual/udev" to "order of items in this new Handbook |
33 |
page", we still need to decide what the default is don't we? |
34 |
|
35 |
|
36 |
|
37 |
-----BEGIN PGP SIGNATURE----- |
38 |
Version: GnuPG v2 |
39 |
|
40 |
iF4EAREIAAYFAla4ye0ACgkQAJxUfCtlWe0fQQEAhwlNL4UR7OCHwQrIspTJjan0 |
41 |
eRcokUvWl4VSq7BZtjoA/AszQTLuS3AXB4hTB7Vd/fndJ1y+YrbNw1Z+V/pF4tNa |
42 |
=0G1K |
43 |
-----END PGP SIGNATURE----- |