Gentoo Logo
Gentoo Spaceship

Installation:
Gentoo Handbook
Installation Docs

Documentation:
Home
Listing
About Gentoo
Philosophy
Social Contract

Resources:
Bug Tracker
Developer List
Discussion Forums
Gentoo BitTorrents
Gentoo Linux Enhancement Proposals
IRC Channels
Mailing Lists
Mirrors
Name and Logo Guidelines
Online Package Database
Security Announcements
Staffing Needs
Supporting Vendors
View our CVS

Graphics:
Logos and themes
Icons
ScreenShots

Miscellaneous Resources:
Gentoo Linux Store
Gentoo-hosted projects
IBM dW/Intel article archive




List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Rémi Cardona <remi@g.o>
Subject: Re: RFC: best way to introduce USE=prefix
Date: Sat, 04 Apr 2009 14:22:09 +0200
Le 03/04/2009 16:47, Jeremy Olexa a écrit :
> However, we have toyed with other ideas. One of which is to introduce
> IUSE=prefix in prefix.eclass similar to the USE=multilib approach. I
> don't really like this idea because it exposes the use flag and we
> don't want it exposed to the users.

Just of curiosity, with IUSE=prefix, how many packages would get the USE 
flag?

If we're only talking about a few packages, I don't mind it showing up 
in portage. If anything, it'll help spread the word about Prefix :)

Cheers,

Rémi


Replies:
Re: RFC: best way to introduce USE=prefix
-- Fabian Groffen
References:
RFC: best way to introduce USE=prefix
-- Jeremy Olexa
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: RFC: best way to introduce USE=prefix
Next by thread:
Re: RFC: best way to introduce USE=prefix
Previous by date:
Re: RFC: best way to introduce USE=prefix
Next by date:
Real multilib support for Gentoo


Updated Aug 18, 2009

Donate to support our development efforts.

Gentoo Centric Hosting: vr.org

VR Hosted

Tek Alchemy

Tek Alchemy

SevenL.net

SevenL.net

php|architect

php|architect

Copyright 2001-2007 Gentoo Foundation, Inc. Questions, Comments? Email www@gentoo.org.