From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10458 invoked by uid 1002); 5 Jul 2003 17:38:39 -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 27170 invoked from network); 5 Jul 2003 17:38:37 -0000 Date: Sat, 5 Jul 2003 23:08:19 +0530 From: Devdas Bhagat To: gentoo-dev@gentoo.org Message-ID: <20030705230819.A19959@evita.devdas.geek> Reply-To: Devdas Bhagat Mail-Followup-To: gentoo-dev@gentoo.org References: <20030701025824.64ecc18a.seemant@gentoo.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-rmd160; protocol="application/pgp-signature"; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030701025824.64ecc18a.seemant@gentoo.org>; from seemant@gentoo.org on Tue, Jul 01, 2003 at 02:58:24AM -0700 Subject: Re: [gentoo-dev] Interest Check: Dynamic config files for portage X-Archives-Salt: 38daedf7-a94a-4ca8-ab53-38f340726994 X-Archives-Hash: 18906ef25b1feea36fc051e9714bb600 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 01/07/03 02:58 -0700, Seemant Kulleen wrote: > Hi All, > Before I go and invalidate a bug, I thought I might take the idea=20 > around here to see if it has any merit in terms of usefulness/interest. >=20 > The idea stems from the fact that etc-updating a make.conf file can be a= =20 > bit of a stressful event. And as portage's set of features grows, so=20 > too will the size of the make.conf file. I get the impression that the= =20 > make.conf file is a little hard to parse, with the huge comment blocks=20 > etc etc. So my proposal is this: a make.conf.d directory which contains= =20 > files for each section of the make.conf: use, flags, fetch, packagevars. Instead of a make.conf.d or make.d, why not ship with a set of sample-make.foo.conf files? The detailed comments can go in the sample files, while the main make.conf has a few short comments. I would suggest make.conf.global and make.conf.local. The global file will summarily be overwritten by any upgrades, the make.conf.local file will never be touched by it. make.conf will include make.conf.global and make.conf.local make.conf.local can have flags set in two ways: append to flags in global: foo +=3D flag flag flag override global flags bar =3D flag flag flag If there are two conflicting flags, the flags in .local take precedence, with a warning logged to the user. This should enable you not to have to bother about what has changed, while allowing for local configuration specific customization. Devdas Bhagat --sdtB3X0nJg68CQEu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/Bw0K/SCOKCzbZtsRAjsfAKCIs2olpoT/G+euORGvwLDmkPsJIQCfdDJ+ aajyBvrrMtLmA70GpTydO+U= =QyYO -----END PGP SIGNATURE----- --sdtB3X0nJg68CQEu--