From: Joe Peterson <lavajoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] New RESTRICT=live value for identification of live ebuilds?
Date: Sun, 03 Aug 2008 15:59:37 -0600 [thread overview]
Message-ID: <48962A49.5080102@gentoo.org> (raw)
In-Reply-To: <48962894.8060409@gentoo.org>
Zac Medico wrote:
> Personally I think people are far too concerned about the name of
> the variable. I only see a what I consider to be a trivial or
> negligible benefit in separating these things into two different
> variables. However, it it makes more people happy then I guess I'm
> for it.
Different people have differing sensitivity to things like this
(aesthetics, consistency, etc.). IMHO, this particular one is not a
*huge* deal (picking my battles, I personally would not choose to be too
vehement on this one), but it's always nice to pick the most
elegant/logical way to do things, especially for things that are exposed
to the dev/ebuild interface and are hard to change later.
-Joe
next prev parent reply other threads:[~2008-08-03 21:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aWLOY-34G-11@gated-at.bofh.it>
[not found] ` <aWLOY-34G-13@gated-at.bofh.it>
[not found] ` <aWLOY-34G-15@gated-at.bofh.it>
[not found] ` <aWLOY-34G-17@gated-at.bofh.it>
[not found] ` <aWLOY-34G-19@gated-at.bofh.it>
[not found] ` <aWLOY-34G-9@gated-at.bofh.it>
[not found] ` <aWMrG-4Dh-21@gated-at.bofh.it>
2008-08-03 14:55 ` [gentoo-dev] [RFC] New RESTRICT=live value for identification of live ebuilds? Vaeth
2008-08-03 15:18 ` Joe Peterson
2008-08-03 20:04 ` Zac Medico
2008-08-03 20:48 ` Zac Medico
2008-08-03 21:45 ` Joe Peterson
2008-08-03 21:52 ` Zac Medico
2008-08-03 21:59 ` Joe Peterson [this message]
2008-08-03 22:02 ` Zac Medico
2008-08-03 22:53 ` Zac Medico
[not found] <aWeJm-70R-13@gated-at.bofh.it>
[not found] ` <aWzEa-6Dc-3@gated-at.bofh.it>
[not found] ` <aWA79-785-1@gated-at.bofh.it>
[not found] ` <aWBwe-Xt-5@gated-at.bofh.it>
[not found] ` <aWBPx-1iE-5@gated-at.bofh.it>
2008-08-03 13:28 ` Vaeth
2008-08-03 14:02 ` Zac Medico
2008-08-02 2:02 Zac Medico
2008-08-02 4:58 ` Luis Francisco Araujo
2008-08-02 9:10 ` Mike Auty
2008-08-02 10:26 ` Zac Medico
2008-08-02 12:14 ` Mike Auty
2008-08-02 22:34 ` Zac Medico
2008-08-02 23:07 ` René 'Necoro' Neumann
2008-08-02 23:31 ` Zac Medico
2008-08-02 23:49 ` René 'Necoro' Neumann
2008-08-03 0:03 ` Luis Francisco Araujo
2008-08-02 15:03 ` Santiago M. Mola
2008-08-02 22:25 ` Zac Medico
2008-08-03 19:02 ` Santiago M. Mola
2008-08-02 9:19 ` Arfrever Frehtes Taifersar Arahesis
2008-08-02 10:12 ` Zac Medico
2008-08-02 23:06 ` Zac Medico
2008-08-02 23:49 ` Luca Barbato
2008-08-03 0:07 ` Nirbheek Chauhan
2008-08-03 0:07 ` Avuton Olrich
2008-08-03 1:09 ` Zac Medico
2008-08-03 0:19 ` Thomas de Grenier de Latour
2008-08-03 0:59 ` Zac Medico
2008-08-03 2:27 ` Thomas de Grenier de Latour
2008-08-03 2:49 ` Zac Medico
2008-08-06 10:36 ` Marius Mauch
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=48962A49.5080102@gentoo.org \
--to=lavajoe@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