| 1 |
On Sun, 28 Dec 2003 15:39:48 -0700 |
| 2 |
Daniel Robbins <drobbins@g.o> wrote: |
| 3 |
|
| 4 |
> This change was not officially on our roadmap, but yep, it should |
| 5 |
> start happening with Gentoo 2004 provided that a trimmed |
| 6 |
> /etc/make.conf will work for our arch leads. I think it's a great way |
| 7 |
> to reduce clutter, and with the info in the Handbook I don't see any |
| 8 |
> real negatives. |
| 9 |
> |
| 10 |
|
| 11 |
I do not agree on this point. |
| 12 |
|
| 13 |
Think that many users are lazy and will not check handbook is something |
| 14 |
has changed. For examples, I sometimes have to add or remove advices |
| 15 |
about CHOST, CFLAGS and CXXFLAGS in make.conf because toolchain or |
| 16 |
something else is more or less stable than before with some settings. |
| 17 |
|
| 18 |
I also like to to have the documentation near what I'm modifying. And |
| 19 |
it's also great to have the exaustive list of every variables that you |
| 20 |
can change in this file. |
| 21 |
|
| 22 |
Starting your browser and try to find the info you need in the handbook |
| 23 |
takes really much time if for example you only want to change the temp |
| 24 |
dir and you don't remember if the correct syntax is PORDIR_TEMP, |
| 25 |
PORTDIR_TMP or PORTAGE_TMPDIR. |
| 26 |
|
| 27 |
Also, it's really easier to uncomment a valid example in make.conf than |
| 28 |
copy/past if you are reading a printed doc or watch the handbook on |
| 29 |
another computer for whichever reason. |
| 30 |
|
| 31 |
It's also easy for a newbie or an inattentive person to read the doc of |
| 32 |
another arch in the handbook while the make.conf is arch specific. |
| 33 |
|
| 34 |
|
| 35 |
So please, keep the old make.conf right in place for all this reasons. |
| 36 |
|
| 37 |
|
| 38 |
TIA |
| 39 |
|
| 40 |
-- |
| 41 |
Guy Martin |
| 42 |
Gentoo Linux - HPPA port Lead / IPv6 team |
| 43 |
Lug Charleroi (Belgium) |
| 44 |
|
| 45 |
-- |
| 46 |
gentoo-releng@g.o mailing list |
Archives