From: Dror Levin <spatz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] pkg_pretend USE validation and VALID_USE alternative
Date: Thu, 1 Apr 2010 21:39:43 +0300 [thread overview]
Message-ID: <s2o2becdd071004011139n5e9c70d0qaa6681020e3da19a@mail.gmail.com> (raw)
In-Reply-To: <201004011804.49097.levertond@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
On Thu, Apr 1, 2010 at 20:04, David Leverton <levertond@googlemail.com>wrote:
> If anyone's been personal and insulting in this discussion, it isn't
> Ciaran.
>
I'll take that as an April Fools' day joke.
> As for the topic: the only real concern about VALID_USE that I've seen from
> anyone is about whether Portage can implement it reasonably soon. Since
> some
> people think it can, how about picking some reasonable time period
> (allowing
> for bikeshedding about the syntax, of course), and if VALID_USE isn't
> supported in Portage by then but EAPI 4 is otherwise ready then we postpone
> VALID_USE until later?
>
Here's another suggestion: how about we don't impose any ridiculous
constraints on development and keep this discussion on the technological
side of the original proposal? If the only concerns are about the time it
will take to implement, then this suggestion must be perfect in all aspects
and so we should probably wait until it's done, even if is takes a loooong
time!
I really like this attitude, though. Once you're done criticizing the
technological aspects of some proposal you start raising concerns about how
hard it is to implement features for Portage, how long that takes, etc.
Well, since that's not really constructive, I suggest you keep those
concerns to yourself.
Dror Levin
[-- Attachment #2: Type: text/html, Size: 1862 bytes --]
next prev parent reply other threads:[~2010-04-01 18:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:20 [gentoo-dev] pkg_pretend USE validation and VALID_USE alternative Brian Harring
2010-03-31 9:48 ` [gentoo-dev] Re: [gentoo-council] " Ulrich Mueller
2010-03-31 10:46 ` Brian Harring
2010-03-31 11:04 ` [gentoo-dev] " Ulrich Mueller
2010-03-31 11:11 ` Brian Harring
2010-03-31 15:38 ` "Paweł Hajdan, Jr."
2010-03-31 11:18 ` [gentoo-dev] Re: [gentoo-council] " Piotr Jaroszyński
2010-04-01 20:44 ` Róbert Čerňanský
2010-04-01 21:51 ` Zac Medico
[not found] ` <201003312316.23806.ali_bush@gentoo.org>
2010-03-31 10:57 ` Brian Harring
2010-03-31 17:49 ` [gentoo-dev] " Alex Alexander
2010-03-31 19:46 ` Brian Harring
2010-03-31 19:56 ` Ciaran McCreesh
2010-04-01 7:31 ` Brian Harring
2010-04-01 7:41 ` Ciaran McCreesh
2010-04-01 7:56 ` Brian Harring
2010-04-01 10:10 ` Gilles Dartiguelongue
2010-04-01 10:18 ` Brian Harring
2010-04-01 10:42 ` Gilles Dartiguelongue
2010-04-01 10:59 ` Brian Harring
2010-04-01 11:23 ` Ciaran McCreesh
2010-04-01 11:38 ` Brian Harring
2010-04-01 11:50 ` Ciaran McCreesh
2010-04-01 10:49 ` Ciaran McCreesh
2010-04-01 11:18 ` Brian Harring
2010-04-01 11:44 ` Ciaran McCreesh
2010-04-01 17:04 ` David Leverton
2010-04-01 18:39 ` Dror Levin [this message]
2010-04-01 18:55 ` Ciaran McCreesh
2010-04-02 22:36 ` David Leverton
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=s2o2becdd071004011139n5e9c70d0qaa6681020e3da19a@mail.gmail.com \
--to=spatz@gentoo.org \
--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