Gentoo Archives: gentoo-dev

From: Brian Dolbec <dolsen@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Changing order of default virtual/udev provider
Date: Mon, 08 Feb 2016 17:33:09
Message-Id: 20160208093155.0f0cb74e.dolsen@gentoo.org
In Reply to: Re: [gentoo-dev] Changing order of default virtual/udev provider by Ian Stakenvicius
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA512
3
4 On Mon, 8 Feb 2016 12:01:33 -0500
5 Ian Stakenvicius <axs@g.o> wrote:
6
7 > -----BEGIN PGP SIGNED MESSAGE-----
8 > Hash: SHA256
9 >
10 > On 08/02/16 11:18 AM, Rich Freeman wrote:
11 > > However, I think we're actually missing the bigger issue here.
12 > > Why is this virtual even in @system to begin with? When I set up
13 > > a chroot or some kinds of containers I don't need udev, or
14 > > sysvinit (or openssh - but let's set that one aside for now).
15 > >
16 > > We don't stick grub or genkernel or even gentoo-sources in our
17 > > stage3s. Why stick (e)udev in there?
18 > >
19 > > It seems like this should just be another step in the handbook -
20 > > pick your desired device manager.
21 > >
22 > > Obviously if we produce a boot CD it will need a device manager
23 > > (and kernel and bootloader and network manager), and I don't care
24 > > which one it is.
25 > >
26 > > This just seems more like the Gentoo way, and it completely
27 > > sidesteps all the controversy over defaults. We're already
28 > > working on fixing the few remaining functions.sh references so
29 > > that openrc can be removed from the system set as well.
30 > >
31 >
32 > I thought the point of this discussion had to do mostly with what
33 > udev variant gets installed when a user doesn't specify one. And
34 > AFAIK, since there are still plenty of packages that *DEPEND on
35 > virtual/udev , the discussion's still worth having isn't it?
36 >
37 > Besides, if we just move the goal of this discussion from "order of
38 > atoms in virtual/udev" to "order of items in this new Handbook
39 > page", we still need to decide what the default is don't we?
40
41
42 Yes, we do.
43
44 Also, it is releng's intention to change to a stage4 for normal new
45 install stages. It will contain the most needed pkgs for new installs,
46 and allow the @system set to be trimmed down more. It is entirely
47 possible, to at that point, then create smaller chroot/container images
48 without undue hardships and complexities for new installs.
49
50 But please let's not sidetrack this thread more with this tangent.
51 That's a different bikeshed to paint.
52
53
54
55 - --
56 Brian Dolbec <dolsen>
57
58 -----BEGIN PGP SIGNATURE-----
59 Version: GnuPG v2.1
60
61 iQJ8BAEBCgBmBQJWuNEMXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
62 ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNUQ3Qzc0RTA4MUNDNzBEQjRBNEFBRjVG
63 QkJEMDg3Mjc1ODIwRUQ4AAoJEPu9CHJ1gg7YTVQQAJhStpgaDT2pqMsVuTO3HZx6
64 XfaZoNtcN01nqOttBwQ4C+17n8Rv2/d52Zu6lc3YSrdPgHRGOVT0LU8CyzZlz8Rw
65 rnFeo5oZAZheqlA/4UzRMOkhXbOvT4FRDL1bF/q5t00h+pADoPDSC3ZIyS8enkvr
66 Evm3DYpDDT40pM5f7cwlAqRarJL604XDgFmU5Qhtmtnxw+TRIicGTwHoWe4fk77u
67 PNm3ZrU+ea7b2XAwKH+oDVM0UDMfFLi37APGd4R2VC0jJmp0msPnNfKRvpURcNo5
68 3iZMMDuM7vqJergB2yCfiqaGdHmaEPX1PLpQEuhgLWS0b6lCN4JKenYpRdNVLjZG
69 FqOEtSVUs9iNt++XmsZ6goLQAczePOxqR/aAJOMrXuhePiuXMRmm1MBQK2yRRo6q
70 6MU/lj+1YAzEWMyOZH9GNzQhCl1cBj+futm6mRTWYsNCaKOGi/ocnIHiQpXyKf/U
71 dp/hlvx2rhqMz6eqO60OaJHaKzbCV6EbGb3kv0AsC4VGGFS+DpoUen21aetBh82O
72 aE6c/hKNvsgARQl0mpwFDttSnB24oRr8E9pR5Rvf7iQJwL7h/5gHvs2YQRL9PxFR
73 vSN1R67Sge9JrAzQ/OmEBbl5exO2a1/0HShfdfvU6oA/lDShFHyttJXYxGi0tDym
74 A2Bo/b9FonL7aEmwilCH
75 =PiEj
76 -----END PGP SIGNATURE-----