On Thu, 2005-08-25 at 00:28 -0400, Mike Frysinger wrote:
- base doesnt define any USE
- default-linux defines a few local xorg USE (because no one has given us the
ability to control default USE via IUSE yet :P)
{x86,amd64}/make.defaults has the 'bloated' USE because every single sub x86
Chris Gianelloni wrote:
On Thu, 2005-08-25 at 00:28 -0400, Mike Frysinger wrote:
- base doesnt define any USE
- default-linux defines a few local xorg USE (because no one has given us the
ability to control default USE via IUSE yet :P)
{x86,amd64}/make.defaults has the 'bloated' USE
Hola all.
Out of curiousity, since for once my portage installation is *not*
filtering out all flags but my own, I'm wondering why it is that the
system default now holds a lot of use flags that aren't really related
to the system set of packages.
See, from my standpoint cascaded profiles
On Wednesday 24 August 2005 08:04 pm, Brian Harring wrote:
Again, returning to the USE=-* arguement, yes, they can go that
route. It's also kind of a crappy arguement dodging out of the fact that
progressive bloat going into what is effectively a base release
profile, when subprofiles would
On Wed, Aug 24, 2005 at 08:50:58PM -0400, Mike Frysinger wrote:
On Wednesday 24 August 2005 08:04 pm, Brian Harring wrote:
Again, returning to the USE=-* arguement, yes, they can go that
route. It's also kind of a crappy arguement dodging out of the fact that
progressive bloat going into
Brian Harring wrote:
On Wed, Aug 24, 2005 at 08:50:58PM -0400, Mike Frysinger wrote:
On Wednesday 24 August 2005 08:04 pm, Brian Harring wrote:
Again, returning to the USE=-* arguement, yes, they can go that
route. It's also kind of a crappy arguement dodging out of the fact that
progressive
On Wednesday 24 August 2005 09:27 pm, Brian Harring wrote:
On Wed, Aug 24, 2005 at 08:50:58PM -0400, Mike Frysinger wrote:
On Wednesday 24 August 2005 08:04 pm, Brian Harring wrote:
Again, returning to the USE=-* arguement, yes, they can go that
route. It's also kind of a crappy
