From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19783 invoked by uid 1002); 18 Nov 2002 20:32:12 -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 19761 invoked from network); 18 Nov 2002 20:32:11 -0000 From: Stefan Jones To: gentoo-dev , gentoo-core In-Reply-To: <20021118174159.GB18401@linuxpimpz.com> References: <1037541053.25487.58.camel@localhost> <3DD8FECF.7030508@yahoo.com.br> <20021118174159.GB18401@linuxpimpz.com> Content-Type: text/plain Organization: Gentoo Linux Message-Id: <1037651472.3049.24.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 18 Nov 2002 20:31:12 +0000 Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] Prelinking in Gentoo and interactions with portage X-Archives-Salt: 69a9c588-806f-40c1-a69d-31f60affea24 X-Archives-Hash: 965542990ccfef889e55bc3d19ad6661 On Mon, 2002-11-18 at 17:41, David Olsen wrote: > On 2002-11-18-09:53:03, Felipe Ghellar wrote: > > What about including it in the variable FEATURES in make.conf? > > > > FEATURES="sandbox ccache prelink" > > Prelinking may be more suited as a USE variable, just an opinion though. > I am siding on the side of "FEATURES" as prelinking globally effects binaries and libraries, you cannot always say that certain libraries are not to be prelinked, as USE flags would imply. Also you would have a messy problem on uninstall having to read the USE flags. Although you could choose to always uninstall in the prelink safe way. Plus it fits better into the portage overview to have USE flags effect the behaviour of the ebuild code and FEATURES flags effect the portage (python) code. My two pence , -- Stefan Jones Gentoo Linux -- gentoo-dev@gentoo.org mailing list