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