* [gentoo-pms] why is '@' allowed in use flags
@ 2010-06-07 5:23 Brian Harring
2010-06-07 7:26 ` Ciaran McCreesh
0 siblings, 1 reply; 4+ messages in thread
From: Brian Harring @ 2010-06-07 5:23 UTC (permalink / raw
To: gentoo-pms
[-- Attachment #1: Type: text/plain, Size: 250 bytes --]
Anyone know where '@' in use flags came from? Last I knew, the
intention of '@' was to be used as a seperator/marker for use groups;
it currently has zero users in gentoo-x86, thus I'm wondering
where/why it was originally allowed.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-pms] why is '@' allowed in use flags
2010-06-07 5:23 [gentoo-pms] why is '@' allowed in use flags Brian Harring
@ 2010-06-07 7:26 ` Ciaran McCreesh
2010-06-07 7:29 ` Brian Harring
0 siblings, 1 reply; 4+ messages in thread
From: Ciaran McCreesh @ 2010-06-07 7:26 UTC (permalink / raw
To: gentoo-pms
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
On Sun, 6 Jun 2010 22:23:03 -0700
Brian Harring <ferringb@gmail.com> wrote:
> Anyone know where '@' in use flags came from? Last I knew, the
> intention of '@' was to be used as a seperator/marker for use groups;
> it currently has zero users in gentoo-x86, thus I'm wondering
> where/why it was originally allowed.
Linguas.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-pms] why is '@' allowed in use flags
2010-06-07 7:26 ` Ciaran McCreesh
@ 2010-06-07 7:29 ` Brian Harring
2010-06-07 7:33 ` Ciaran McCreesh
0 siblings, 1 reply; 4+ messages in thread
From: Brian Harring @ 2010-06-07 7:29 UTC (permalink / raw
To: gentoo-pms
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
On Mon, Jun 07, 2010 at 08:26:47AM +0100, Ciaran McCreesh wrote:
> On Sun, 6 Jun 2010 22:23:03 -0700
> Brian Harring <ferringb@gmail.com> wrote:
> > Anyone know where '@' in use flags came from? Last I knew, the
> > intention of '@' was to be used as a seperator/marker for use groups;
> > it currently has zero users in gentoo-x86, thus I'm wondering
> > where/why it was originally allowed.
>
> Linguas.
Fark. Knew I was forgetting to grep somewhere...
Follow up discussion point; anyone got a character to use for
seperating use_expand groups and their members? I'm well aware '_' is
used right now, but it's use is nonoptimal- the only way to break down
a use_expanded target in IUSE is to know the use_expand grouppings
themselves, which is profile defined... a flaw I've hated since day
one.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [gentoo-pms] why is '@' allowed in use flags
2010-06-07 7:29 ` Brian Harring
@ 2010-06-07 7:33 ` Ciaran McCreesh
0 siblings, 0 replies; 4+ messages in thread
From: Ciaran McCreesh @ 2010-06-07 7:33 UTC (permalink / raw
To: gentoo-pms
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
On Mon, 7 Jun 2010 00:29:46 -0700
Brian Harring <ferringb@gmail.com> wrote:
> Follow up discussion point; anyone got a character to use for
> seperating use_expand groups and their members? I'm well aware '_'
> is used right now, but it's use is nonoptimal- the only way to break
> down a use_expanded target in IUSE is to know the use_expand
> grouppings themselves, which is profile defined... a flaw I've hated
> since day one.
We've been using : in exheres-0.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-06-07 7:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-07 5:23 [gentoo-pms] why is '@' allowed in use flags Brian Harring
2010-06-07 7:26 ` Ciaran McCreesh
2010-06-07 7:29 ` Brian Harring
2010-06-07 7:33 ` Ciaran McCreesh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox