From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Fwd: [gentoo-dev-announce] Call for items for September 13 council meeting
Date: Thu, 15 Sep 2011 16:54:44 -0700 [thread overview]
Message-ID: <20110915235444.GB31364@beast> (raw)
In-Reply-To: <201109160122.00747.Arfrever.FTA@gmail.com>
On Fri, Sep 16, 2011 at 01:21:55AM +0200, Arfrever Frehtes Taifersar Arahesis wrote:
> 2011-09-15 09:55:08 Ciaran McCreesh napisał(a):
> > On Thu, 15 Sep 2011 09:35:21 +0200
> > Michał Górny <mgorny@gentoo.org> wrote:
> > > Could you point me to at least a single program not supporting dots
> > > in useflags? My quick check shows that all PMs handle them well, quse
> > > and euse as well.
> >
> > Hrm, it's rather disappointing that they're accepted everywhere. That
> > really shouldn't happen... My excuse for Paludis is that I never quite
> > got around to passing in additional flags to validation of names, and
> > dots are legal in exheres-0
>
> There is no reason for Gentoo to be worse than Exherbo and not allow dots in USE flags.
Seriously Arfrever, drop the rhetoric here, and go fix the profile
compatibility issue. Everytime you bring up dot's in use, you ignore
compatibility, and every damn time it gets brought up I keep having
to repeat this. It's not productive and this has repeated for at
least a year now.
People who want this need to sort the compat issue rather than
sticking their heads in the sand.
~brian
next prev parent reply other threads:[~2011-09-15 23:55 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E64C7BB.907@gentoo.org>
[not found] ` <CA+Nrkpd499zUJiHee2f9wfoCgRiQCO0EXetowbPdWYmMGoaFkA@mail.gmail.com>
2011-09-07 9:07 ` [gentoo-dev] Fwd: [gentoo-dev-announce] Call for items for September 13 council meeting Tomáš Chvátal
2011-09-07 9:17 ` Andreas K. Hüttel
2011-09-07 13:21 ` Ulrich Mueller
2011-09-07 14:27 ` Tomáš Chvátal
2011-09-07 15:43 ` Michał Górny
2011-09-07 15:48 ` Michał Górny
2011-09-07 22:47 ` Aaron W. Swenson
2011-09-07 22:53 ` Ciaran McCreesh
2011-09-07 23:04 ` Brian Harring
2011-09-15 7:35 ` Michał Górny
2011-09-15 7:55 ` Ciaran McCreesh
2011-09-15 8:01 ` Michał Górny
2011-09-15 8:07 ` Ciaran McCreesh
2011-09-15 23:21 ` Arfrever Frehtes Taifersar Arahesis
2011-09-15 23:54 ` Brian Harring [this message]
2011-09-16 0:20 ` Arfrever Frehtes Taifersar Arahesis
2011-09-16 21:06 ` Zac Medico
2011-09-18 3:47 ` Donnie Berkholz
2011-09-18 5:26 ` Zac Medico
2011-09-18 6:01 ` Brian Harring
2011-09-18 6:57 ` Ulrich Mueller
2011-09-18 9:24 ` Nirbheek Chauhan
2011-09-18 9:33 ` Ciaran McCreesh
2011-09-18 14:20 ` Jorge Manuel B. S. Vicetto
2011-09-18 15:58 ` Ciaran McCreesh
2011-09-18 16:14 ` Rich Freeman
2011-09-18 17:10 ` Nirbheek Chauhan
2011-09-18 17:34 ` Zac Medico
2011-09-18 14:47 ` Michał Górny
2011-09-18 15:54 ` Ciaran McCreesh
2011-09-15 16:51 ` Brian Harring
2011-09-07 16:19 ` Ciaran McCreesh
2011-09-08 17:03 ` Thomas Sachau
2011-09-08 17:41 ` Alec Warner
2011-09-08 17:55 ` Ole Markus With
2011-09-08 18:10 ` Arfrever Frehtes Taifersar Arahesis
2011-09-08 18:35 ` Michał Górny
2011-09-08 18:33 ` Ciaran McCreesh
2011-09-08 18:43 ` Michał Górny
2011-09-09 0:45 ` Mike Frysinger
2011-09-18 11:08 ` proposal for cross-compie support in EAPI-5, was: " Thomas Sachau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110915235444.GB31364@beast \
--to=ferringb@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox