From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17161 invoked by uid 1002); 7 Sep 2003 00:26:16 -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 28089 invoked from network); 7 Sep 2003 00:26:16 -0000 From: Steven Elling To: gentoo-dev@gentoo.org Date: Sat, 6 Sep 2003 19:26:08 -0500 User-Agent: KMail/1.5.2 References: <200309061848.54494.ellings@kcnet.com> <20030906235642.GA22596@cerberus.oppresses.us> In-Reply-To: <20030906235642.GA22596@cerberus.oppresses.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309061926.08828.ellings@kcnet.com> Subject: Re: [gentoo-dev] Some suggestions X-Archives-Salt: 9c5b5337-1d9a-4e2b-85dc-d282fae871f9 X-Archives-Hash: f2e58fa928d010ef50eb5749db2836eb On Saturday 06 September 2003 18:56, Jon Portnoy wrote: > On Sat, Sep 06, 2003 at 06:48:54PM -0500, Steven Elling wrote: > > On Saturday 06 September 2003 13:05, David Sankel wrote: > > > 2) make.conf updates to be more automated > > > > > > Most gentoo users, I believe, modify this file. This specific file > > > changes quite often with updates. Since most users only modify the > > > "USE" and "CFLAGS" components, having an update that is automatic is > > > plausible. This feature is a trade off between the integrity and > > > consistency of the system verses end-user maintenance time. > > > > Requiring portage updates to make.conf at all has always bugged me. > > The file is meant to contain custom settings for portage and to append > > to or override variables in make.globals and the defaults. It should > > not hold all the documentation for make.conf. It should not hold all > > the defaults... that's what make.globals and the defaults are for. > > > > Why is all the documentation on make.conf in make.conf anyway? > > Shouldn't it be in make.globals or better yet the man page? > > > > make.conf is used for system customization and, as such, portage should > > leave it alone. When portage is installed on the drive for the first > > time it should not create make.conf. Portage should leave it up to the > > admin/user of the box to create the file. > > Most users find it very convienent to have all of that information > available to them, especially on an initial install. Additionally, it's > necessary to have that file present for Portage to operate properly, > even if it hasn't been edited. IMHO, it is just as convienent to have the information in the man page. Also, maybe there needs to be a make.conf doc on www.gentoo.org and referenced from the install docs. That way anyone doing an install could print out or view the install and make.conf docs. Even though I've done several installs, I still like to have the install instructions in front of me and a make.conf doc would help. 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. -- gentoo-dev@gentoo.org mailing list