From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25727 invoked by uid 1002); 8 Sep 2003 22:15:20 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 20161 invoked from network); 8 Sep 2003 22:15:20 -0000 From: Steven Elling To: Gentoo-Dev Date: Mon, 8 Sep 2003 17:15:13 -0500 User-Agent: KMail/1.5.2 References: <1062904114.8455.62.camel@nosferatu.lan> <1062952988.27390.12.camel@vertigo> In-Reply-To: <1062952988.27390.12.camel@vertigo> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309081715.13241.ellings@kcnet.com> Subject: Re: [gentoo-dev] Some suggestions X-Archives-Salt: cbc83700-4028-4e76-8230-b55263cd3dca X-Archives-Hash: 214008753fe5c8d4c320b8789dee9c6d On Sunday 07 September 2003 11:43, Chris Gianelloni wrote: > On Sat, 2003-09-06 at 23:08, Martin Schlemmer wrote: > > On Sun, 2003-09-07 at 02:57, Chris Gianelloni wrote: > > > On Sat, 2003-09-06 at 20:26, Steven Elling wrote: > > > > Does portage bomb out if make.conf is not present? If so, maybe > > > > portage needs to be changed so that it will work without the file. > > > > > > I definitely like the idea of creating make.conf docs and a link from > > > the install docs. Also, why can't the portage ebuild contain a 0 > > > byte make.conf file? After all, the file CAN be empty and portage > > > will still work from the make.globals since make.conf serves no > > > purpose but to override the system defaults. We could include a > > > make.conf file in the stage tarballs with a few settings (depending > > > on the settings of the stage) and a comment telling the user where > > > the docs for make.conf are located both locally and on Gentoo.org. > > > > I really do not see how having to either: > > > > 1) Copy and paste everything > > > > 2) Type if from a printout/whatever > > > > is efficient or helps the average user? It is way easier > > to just uncomment and change as needed with the help, etc > > there in front of you. > > A link from the installation docs has already proved its worth. Look at > the USE section of the install docs. They point to the use.xml file. > Why would make.conf be any harder? I also said that the defaults used > in building the stage would be included IN THE STAGE tarball, as it is > now. Only the portage ebuild would contain the "blank" make.conf. All of the defaults for the portage system are in /etc/make.globals and /etc/make.profile/make.defaults. That makes make.conf a config file meant to be used for altering the operation of the portage system or enabling additional functionality. With the documentation being put in the proper place and updated, make.conf should be blank, have a one liner asking the user to read the man page or non-existent until customization it needed. -- gentoo-dev@gentoo.org mailing list