Gentoo Archives: gentoo-user

From: Dale <rdalek1967@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] New network cards default to "Y" with "make oldconfig"
Date: Sun, 24 Mar 2019 19:34:27
Message-Id: 73d254da-98b0-49e5-4315-91e7e7e9dfca@gmail.com
In Reply to: Re: [gentoo-user] New network cards default to "Y" with "make oldconfig" by Rich Freeman
1 Rich Freeman wrote:
2 > On Sun, Mar 24, 2019 at 1:02 PM Dale <rdalek1967@×××××.com> wrote:
3 >> Rich Freeman wrote:
4 >>> Suppose you have an Acme model 1234 network card. You've previously
5 >>> answered Yes to enabling its driver, and No to enabling the Acme model
6 >>> 2345 card.
7 >>>
8 >>> Now a new option comes along to show/hide all the Acme cards. That is
9 >>> a new option, so it has no existing value as far as the config
10 >>> database design goes. If you answer No, then you disable your model
11 >>> 1234 card (without even being asked, because that isn't a new option).
12 >>> If you answer yes then effectively your previous choices remain in
13 >>> effect (model 1234 remains enabled, and model 2345 remains disabled).
14 >>>
15 >> One would think it should ask if you want any ACME drivers first. If
16 >> you say yes then ask which ones you want. If you answer no then disable
17 >> them all and move to the Better-than-nothing drivers next in the list,
18 >> assuming the are alphabetical.
19 > This is exactly what it is doing. There is a new question about
20 > whether you want any ACME drivers. It defaults to Yes. If you answer
21 > Yes then it prompts you for each individual driver, though it will
22 > skip those prompts since you've already answered them.
23 >
24 > If you answer No then it will set all the individual drivers to No
25 > (including the ones you previously set to Yes), and not prompt you
26 > further.
27 >
28 >> Once you get past that driver, nothing
29 >> else should disable the drivers you wanted.
30 > But the drivers you wanted WERE Acme drivers, so if you answered No to
31 > that question why would it prompt for those?
32 >
33 > You can see how defaulting to No on these sorts of questions can be
34 > more dangerous, because it can cause you to reverse decisions you
35 > previously made, while defaulting to Yes on the big questions (that
36 > don't actually build anything), and defaulting to No on the little
37 > questions (which do build things) has the result that if you accept
38 > all the defaults you keep the same kernel build you had before.
39 >
40 > If you answer Yes to whether you want ACME drivers it won't actually
41 > build any drivers - you have to enable those individually, and those
42 > questions presumably still default to No.
43 >
44
45
46 The point I was making is once set to yes, then questions after that
47 should not go back and disable what you said yes too.  If a person goes
48 to the trouble of saying yes, then nothing after that should reverse
49 that option back to no.  From what I understand, if it asks a question
50 later on and you say no, it reverses a previous yes even if you want
51 that first one included.  If nothing else, maybe it should point out a
52 conflict so that a person can check into it further. 
53
54 As with anything tho, if it is done any other way, it to would cause
55 confusion too.  This is nothing new really.  It's like having a option
56 hidden until you enable some other option in another part of the config
57 screen.  You know where the option you want to enable is supposed to be
58 but it is hidden because a option somewhere else isn't enabled.  Then
59 you have to find out what to enable so that you can see the one you
60 want.  I've ran into that a couple times and it is fun to figure out.  lol 
61
62 Dale
63
64 :-)  :-)

Replies