1 |
On Sun, 2003-09-07 at 15:59, Jan Krueger wrote: |
2 |
> On Sunday 07 September 2003 03:08, Martin Schlemmer wrote: |
3 |
> > Come on guys, think what is best for the *distro* (meaning, |
4 |
> > what will work best for the other 90% of users, |
5 |
|
6 |
I'd say 95% of user, but that's just me :P |
7 |
|
8 |
> From my point of view the best for the 90% of users in this case (make.conf) |
9 |
> would be: |
10 |
> 1. a very precise documentation with examples about the user settable things |
11 |
> for make.conf thats accessable via a standard command, like man make.conf or |
12 |
> info make.conf |
13 |
|
14 |
How imprecise and unaccessible is: |
15 |
|
16 |
nano -w /etc/make.conf |
17 |
|
18 |
All settings are commented, and commented well, and it's available using |
19 |
standard commands (you could even use ed or a combination of cat, less, |
20 |
head & tail if you really wanted to) |
21 |
|
22 |
> 2. a clean, easy to read configuration file without mess and things the user |
23 |
> doesnt care about so it is easy for the user (even easier for tools) to |
24 |
> change exactly the setting the user wants to change because it is easier to |
25 |
> identify the place where the change must happen and easier to identify the |
26 |
> values that already are there. |
27 |
|
28 |
OK, I've installed Gentoo on my boxes that many times I know the process |
29 |
pretty much off the top of my head, however I can't remember all of the |
30 |
FEATURES that are available, having them listed in make.conf is |
31 |
beneficial. |
32 |
|
33 |
> You may try this yourself: |
34 |
> nano -w make.conf as it gets installed |
35 |
> |
36 |
> and |
37 |
> nano -w make.conf with just the settings you actually use, everything else |
38 |
> thrown out. |
39 |
|
40 |
grep -v "#" /etc/make.conf|wc -l && wc -l < /etc/make.conf |
41 |
31 |
42 |
290 |
43 |
|
44 |
Fair enough, I've got 259 lines of comments, I can live with that, the |
45 |
file isn't confusing and the options are grouped sensibly. |
46 |
|
47 |
It seems to me to be fairly standard Linux practice to provide a well |
48 |
commented config file that can be modified slightly as suited, eg: |
49 |
|
50 |
grep -v "#" /etc/squid/squid.conf | wc -l && wc -l < |
51 |
/etc/squid/squid.conf |
52 |
258 |
53 |
3231 |
54 |
|
55 |
So, I've got nearly 3000 lines of comments in my squid.conf, I bet you |
56 |
won't see anyone suggesting that squid gets installed with an empty |
57 |
config file and you have to roll one by hand. |
58 |
|
59 |
> Which one is easier to modify? |
60 |
> Especially try to change a FEATURE setting. Or even better, let a new gentoo |
61 |
> user try to change a FEATURE setting. |
62 |
> |
63 |
> If the user is not sure about the variables/values to put there the user may |
64 |
> at anytime suspend nano or open another terminal or use another virtual |
65 |
> console and execute man make.conf |
66 |
|
67 |
So it is easier to explain to a newbie that they need to switch to a |
68 |
new virtual console, start up the documentation viewer (man, less, |
69 |
lynx), read through the docs, switch back to the other virtual console, |
70 |
make a few changes in the file, lather, rinse, repeat. |
71 |
|
72 |
I'll differ with your opinion here, I think it is much easier to have a |
73 |
well commented file (same as reading code, if the comments are in the |
74 |
code, it's easier than referring to a description of it and trying to |
75 |
read the code). |
76 |
|
77 |
> most users probably use just 4 or 5 settings: |
78 |
> use flags |
79 |
> c(xx) flags |
80 |
> sync |
81 |
> mirrors |
82 |
> features |
83 |
|
84 |
True, those are probably the only ones people set, but they are some of |
85 |
the most important ones in the system. |
86 |
|
87 |
Having a config file that lists only the variables to be changed will |
88 |
lead to people swapping conf files ("Here, use this one it is all set |
89 |
and works well for me") which could in turn lead to more problems |
90 |
because people have settings enabled/disabled and they don't know why, |
91 |
or what those things do. |
92 |
|
93 |
> the rest is for the majority of users just useless in make.conf. So my |
94 |
> expirience (and assumption). |
95 |
> |
96 |
> |
97 |
> So i strongly support: |
98 |
> On Saturday 06 September 2003 23:48, Steven Elling wrote: |
99 |
> > Requiring portage updates to make.conf at all has always bugged me. The |
100 |
> > file is meant to contain custom settings for portage and to append to or |
101 |
> > override variables in make.globals and the defaults. It should not hold |
102 |
> > all the documentation for make.conf. It should not hold all the |
103 |
> > defaults... that's what make.globals and the defaults are for. |
104 |
> > |
105 |
> > Why is all the documentation on make.conf in make.conf anyway? Shouldn't |
106 |
> > it be in make.globals or better yet the man page? |
107 |
> > |
108 |
> > make.conf is used for system customization and, as such, portage should |
109 |
> > leave it alone. When portage is installed on the drive for the first time |
110 |
> > it should not create make.conf. Portage should leave it up to the |
111 |
> > admin/user of the box to create the file. |
112 |
> Thats sound like a clean solution to me. Thats the way it should be. |
113 |
|
114 |
Given that a very, very, very large portion of the questions that get |
115 |
fielded on #gentoo are the result of a significant lack of RTF'ing M I |
116 |
don't think having an empty file is the way to go, #gentoo would just |
117 |
degenerate into "RTFM" responses (of which I am pleased to say that |
118 |
generally there are not *that* many). |
119 |
|
120 |
[see above re: swapping of config files as well] |
121 |
|
122 |
> I refuse to update my customised and over the time grown settings in |
123 |
> /etc/make.conf with /etc/make.conf with comments for things i never intend to |
124 |
> use. That doesnt make any sense to me to put such useless comments with |
125 |
> documentation that has to be in the man page anyway in a file thats so |
126 |
> important for my system. |
127 |
> I refuse to let anything automaticly update this file. |
128 |
> I refuse to touch this file until there is a strong need to edit it because i |
129 |
> want a feature/useflag or whatever. So then, and only then, i edit this file |
130 |
> or let a tool edit it (eg: euse). |
131 |
|
132 |
etc-update, merge files, half a dozen l's, a couple of r's, the odd eb |
133 |
and it's all done, new FEATURES merged in, old settings left intact. |
134 |
|
135 |
Not hard, plus I am now aware of what new things are available. |
136 |
|
137 |
> If a change, because of a new advanced portage version, to my existing |
138 |
> settings is needed, this change should be delayed as other software does it: |
139 |
> mark the old thing as deprecated and warn the user for some time|versions to |
140 |
> give the user time to get informed and do the change manually or by using a |
141 |
> dedicated tool. |
142 |
> |
143 |
|
144 |
"Gentoo moves pretty fast; if you don't stop and look around once and |
145 |
awhile, you could miss out." |
146 |
-- |
147 |
Troy Dack "Yes, yes, I know that, Sydney ... Everybody knows that! |
148 |
tad@g.o ... But look: Four wrongs squared, minus two wrongs to |
149 |
the fourth power, divided by this formula, do make a |
150 |
right." -- Gary Larson |
151 |
|
152 |
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4D90BE3C |
153 |
Key fingerprint = 1F3D 6C15 16AA 09D5 0C96 92E5 FD89 16F9 4D90 BE3C |