From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27544 invoked by uid 1002); 7 Sep 2003 14:02:22 -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 2317 invoked from network); 7 Sep 2003 14:02:22 -0000 From: Jan Krueger Organization: microgalaxy.net To: azarah@gentoo.org Date: Sun, 7 Sep 2003 16:07:48 +0000 User-Agent: KMail/1.5.2 Cc: Chris Gianelloni , Steven Elling , Gentoo-Dev , Nick Jones References: <200309071502.27645.jk@microgalaxy.net> <1062940896.8455.113.camel@nosferatu.lan> In-Reply-To: <1062940896.8455.113.camel@nosferatu.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309071607.48759.jk@microgalaxy.net> Subject: Re: [gentoo-dev] Some suggestions X-Archives-Salt: 55677ec5-89b5-49a9-9197-4562655be3bc X-Archives-Hash: fc9878d1bd5a7c64569d47f6ac6ddb62 On Sunday 07 September 2003 13:21, Martin Schlemmer wrote: > The other side of the issue that nobody really touched (or wanted to) > up to now, is that the way of doing things as we do is with a reason. > What about proposing (with maybe prototype) a new way of doing what > we do now via CONFIG_PROTECT and etc-update/dispatch-conf that will > also fit the requirements that you guys want ? Ok, as is understand this would be the variable: CONFIG_EXCLUDE in /etc/make.conf This variable would accept a list of directories/files for which the behaviour of portage would be like follows: whenever portage has the image of the to install software ready it scans this image for the values in CONFIG_EXCLUDE. whenever it finds such a directory/file in the image it moves the directory/file to the doc-directory (eg: /usr/share/doc/${PF}/excluded_config/ ) of the image (and maybe writes a message to the user/log) after that portage continues normally. (btw: i really dont like the possibility an ebuild can change the live filesystem in pkg_postinst. that somehow makes the sandbox useless. it shudders me, when i think of an ebuild that has a complicated shell code in pkg_postinst with rm/cp/mv/cat/(other potentially dangerous commands) in it. I just can hope that this shell code works as expected on the wide variations of gentoo installations. but thats another story and another reason why i dont use gentoo on my servers any longer) Jan -- gentoo-dev@gentoo.org mailing list