public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "René 'Necoro' Neumann" <lists@necoro.eu>
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 01:07:38 +0200	[thread overview]
Message-ID: <4894E8BA.9020904@necoro.eu> (raw)
In-Reply-To: <4894E102.6020300@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Zac Medico schrieb:
> I chose "live" because I think it's easy for people to associate it
> with "live ebuilds", which I believe is a common term used to refer
> to ebuild that download live sources in src_unpack. What's in a name
> though? I'll gladly use whatever name satisfies the most people.

Why not rename "live" to something which makes more sense in the
RESTRICT environment? Like the "constant-source" suggestion by Arfrever?
Because for me 'RESTRICT="live"' reads like: "Live(-builds)" are not
possible with this ebuild.

Pushing random boolean flags in a variable, just because it already
happens to be there, seems (for me) to be the wrongest possible
approach. This would be quite similar to: We want to store the ebuild's
author in the ebuild... Hmm - we would need an additional string
variable for this ... Come - let's use the IUSE variable - there are
already strings in there (perhaps add an '@' before the author so we can
parse it).

Just my 2ct,
René
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiU6LkACgkQ4UOg/zhYFuBrVgCfRs/69DxNBy3TN0fsLr20gURW
BxMAnie5SoBzbKN6n2oMhOJvMywV1ydf
=aOCm
-----END PGP SIGNATURE-----



  reply	other threads:[~2008-08-02 23:07 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02  2:02 [gentoo-dev] [RFC] New RESTRICT=live value for identification of live ebuilds? 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 [this message]
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  8:40       ` [gentoo-dev] " Duncan
2008-08-03  8:57         ` Zac Medico
2008-08-03 13:04           ` Duncan
2008-08-03  0:07 ` [gentoo-dev] " 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
     [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
     [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             ` 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
2008-08-03 22:02                       ` Zac Medico
2008-08-03 22:53                       ` Zac Medico

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=4894E8BA.9020904@necoro.eu \
    --to=lists@necoro.eu \
    --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