| 1 |
On Sunday 07 September 2003 11:43, Chris Gianelloni wrote: |
| 2 |
> On Sat, 2003-09-06 at 23:08, Martin Schlemmer wrote: |
| 3 |
> > On Sun, 2003-09-07 at 02:57, Chris Gianelloni wrote: |
| 4 |
> > > On Sat, 2003-09-06 at 20:26, Steven Elling wrote: |
| 5 |
> > > > Does portage bomb out if make.conf is not present? If so, maybe |
| 6 |
> > > > portage needs to be changed so that it will work without the file. |
| 7 |
> > > |
| 8 |
> > > I definitely like the idea of creating make.conf docs and a link from |
| 9 |
> > > the install docs. Also, why can't the portage ebuild contain a 0 |
| 10 |
> > > byte make.conf file? After all, the file CAN be empty and portage |
| 11 |
> > > will still work from the make.globals since make.conf serves no |
| 12 |
> > > purpose but to override the system defaults. We could include a |
| 13 |
> > > make.conf file in the stage tarballs with a few settings (depending |
| 14 |
> > > on the settings of the stage) and a comment telling the user where |
| 15 |
> > > the docs for make.conf are located both locally and on Gentoo.org. |
| 16 |
> > |
| 17 |
> > I really do not see how having to either: |
| 18 |
> > |
| 19 |
> > 1) Copy and paste everything |
| 20 |
> > |
| 21 |
> > 2) Type if from a printout/whatever |
| 22 |
> > |
| 23 |
> > is efficient or helps the average user? It is way easier |
| 24 |
> > to just uncomment and change as needed with the help, etc |
| 25 |
> > there in front of you. |
| 26 |
> |
| 27 |
> A link from the installation docs has already proved its worth. Look at |
| 28 |
> the USE section of the install docs. They point to the use.xml file. |
| 29 |
> Why would make.conf be any harder? I also said that the defaults used |
| 30 |
> in building the stage would be included IN THE STAGE tarball, as it is |
| 31 |
> now. Only the portage ebuild would contain the "blank" make.conf. |
| 32 |
|
| 33 |
All of the defaults for the portage system are in /etc/make.globals and |
| 34 |
/etc/make.profile/make.defaults. That makes make.conf a config file meant |
| 35 |
to be used for altering the operation of the portage system or enabling |
| 36 |
additional functionality. With the documentation being put in the proper |
| 37 |
place and updated, make.conf should be blank, have a one liner asking the |
| 38 |
user to read the man page or non-existent until customization it needed. |
| 39 |
|
| 40 |
|
| 41 |
-- |
| 42 |
gentoo-dev@g.o mailing list |
Archives