On 22:21 Sat 18 Dec , Ciaran McCreesh wrote:
> On Fri, 17 Dec 2010 20:48:26 -0600
> Donnie Berkholz wrote:
> > I don't know of anyone who's actually done this, but setting IUSE
> > based on ACCEPT_KEYWORDS being ~arch should be possible. There may be
> > better or easier solutions.
>
> Uhm...
On Fri, 17 Dec 2010 20:48:26 -0600
Donnie Berkholz wrote:
> I don't know of anyone who's actually done this, but setting IUSE
> based on ACCEPT_KEYWORDS being ~arch should be possible. There may be
> better or easier solutions.
Uhm... IUSE has to be metadata-invariant.
--
Ciaran McCreesh
sign
On 12/18/2010 01:57 AM, Fabian Groffen wrote:
> On 18-12-2010 02:45:06 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
>>
>> Problem #1: USE flags cannot contain "." characters.
>>
>> The following solutions have been suggested:
>> - Add support for "." characters in USE flags in EAPI="4".
>
> L
On 18-12-2010 02:45:06 +0100, Arfrever Frehtes Taifersar Arahesis wrote:
>
> Problem #1: USE flags cannot contain "." characters.
>
> The following solutions have been suggested:
> - Add support for "." characters in USE flags in EAPI="4".
Like Donnie said, this feels like a purely cosmetic chan
2010-12-18 03:48:26 Donnie Berkholz napisał(a):
> On 02:45 Sat 18 Dec , Arfrever Frehtes Taifersar Arahesis wrote:
> > Problem #1: USE flags cannot contain "." characters.
>
> This isn't a problem, it's an arbitrary statement of an antifeature. My
> understanding of the actual problem here is
On 02:45 Sat 18 Dec , Arfrever Frehtes Taifersar Arahesis wrote:
> Problem #1: USE flags cannot contain "." characters.
This isn't a problem, it's an arbitrary statement of an antifeature. My
understanding of the actual problem here is that you want to have some
sort of USE flags for various
This is the summary of some problems and suggested new features in EAPI="4",
which would solve
these problems.
Problem #1: USE flags cannot contain "." characters.
The following solutions have been
