| 1 |
On Saturday 06 September 2003 18:56, Jon Portnoy wrote: |
| 2 |
> On Sat, Sep 06, 2003 at 06:48:54PM -0500, Steven Elling wrote: |
| 3 |
> > On Saturday 06 September 2003 13:05, David Sankel wrote: |
| 4 |
> > > 2) make.conf updates to be more automated |
| 5 |
> > > |
| 6 |
> > > Most gentoo users, I believe, modify this file. This specific file |
| 7 |
> > > changes quite often with updates. Since most users only modify the |
| 8 |
> > > "USE" and "CFLAGS" components, having an update that is automatic is |
| 9 |
> > > plausible. This feature is a trade off between the integrity and |
| 10 |
> > > consistency of the system verses end-user maintenance time. |
| 11 |
> > |
| 12 |
> > Requiring portage updates to make.conf at all has always bugged me. |
| 13 |
> > The file is meant to contain custom settings for portage and to append |
| 14 |
> > to or override variables in make.globals and the defaults. It should |
| 15 |
> > not hold all the documentation for make.conf. It should not hold all |
| 16 |
> > the defaults... that's what make.globals and the defaults are for. |
| 17 |
> > |
| 18 |
> > Why is all the documentation on make.conf in make.conf anyway? |
| 19 |
> > Shouldn't it be in make.globals or better yet the man page? |
| 20 |
> > |
| 21 |
> > make.conf is used for system customization and, as such, portage should |
| 22 |
> > leave it alone. When portage is installed on the drive for the first |
| 23 |
> > time it should not create make.conf. Portage should leave it up to the |
| 24 |
> > admin/user of the box to create the file. |
| 25 |
> |
| 26 |
> Most users find it very convienent to have all of that information |
| 27 |
> available to them, especially on an initial install. Additionally, it's |
| 28 |
> necessary to have that file present for Portage to operate properly, |
| 29 |
> even if it hasn't been edited. |
| 30 |
|
| 31 |
IMHO, it is just as convienent to have the information in the man page. |
| 32 |
Also, maybe there needs to be a make.conf doc on www.gentoo.org and |
| 33 |
referenced from the install docs. That way anyone doing an install could |
| 34 |
print out or view the install and make.conf docs. Even though I've done |
| 35 |
several installs, I still like to have the install instructions in front of |
| 36 |
me and a make.conf doc would help. |
| 37 |
|
| 38 |
Does portage bomb out if make.conf is not present? If so, maybe portage |
| 39 |
needs to be changed so that it will work without the file. |
| 40 |
|
| 41 |
|
| 42 |
-- |
| 43 |
gentoo-dev@g.o mailing list |
Archives