From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6113 invoked by uid 1002); 8 Sep 2003 15:57:30 -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 11418 invoked from network); 8 Sep 2003 15:57:29 -0000 From: Nathaniel To: Gentoo-Dev In-Reply-To: <200309070559.21887.jk@microgalaxy.net> References: <1062896271.20020.28.camel@vertigo> <1062904114.8455.62.camel@nosferatu.lan> <200309070559.21887.jk@microgalaxy.net> Content-Type: text/plain Organization: Bestweb Internet Message-Id: <1063036644.3316.32.camel@glyph.bestweb.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 08 Sep 2003 11:57:25 -0400 Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] Some suggestions X-Archives-Salt: 8d5d012a-14f6-435c-b5e2-62d5fa7c5956 X-Archives-Hash: 6be67dcaba0cadfa02e9a29f4792cb97 Regarding the etc-update issue, here are some of my thoughts. 1. etc-update should check modify dates and overwrite if not modified. 2. Part of the problem is that make.conf has so many options (ie. its a large file.) What if we split it up into smaller files... Something like: /etc/make.conf.d/USE /etc/make.conf.d/CFLAGS ... /etc/make.conf.d/FEATURES etc... I would guess that a large portion of users never modify the features and other settings of make.conf. This way, etc-update could update only the portions that need updating without overwriting USE flags, etc. This would also make it easier to parse the files for any automated install (GLIS), etc. 3. Another option is to have a file that contains the users settings, seperate from config files themselves... For instance, what if we had a file, say /etc/customsettings, that contained all the updated options for config files. It could perhaps contain a syntax like the following: /etc/make.conf:USE="X gnome gtk alsa" /etc/make.conf:FEATURES="distcc sandbox buildpkg" /etc/conf.d/net:IFACE="dhcp" Then etc-update could not only replace the old file with the update, but could also update it with the user's specific values. It could find the line with the "USE=" text and replace it with the full customized replacement. My $.02. -- Nathaniel McCallum npmccallum@users.sourceforge.net http://glis.sourceforge.net -- gentoo-dev@gentoo.org mailing list