public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: [RFC] New RESTRICT=live value for identification of live ebuilds?
Date: Sun, 3 Aug 2008 13:04:33 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.08.03.13.04.33@cox.net> (raw)
In-Reply-To: 48957310.2050606@gentoo.org

Zac Medico <zmedico@gentoo.org> posted 48957310.2050606@gentoo.org,
excerpted below, on  Sun, 03 Aug 2008 01:57:52 -0700:

> I don't like RESTRICT=tarballs because I don't think it's clear enough.
> I think we should go with RESTRICT="live-sources". Maybe it doesn't fit
> your convention, I'm pretty sure we already have other RESTRICT flags
> that don't fit your convention. How about "primaryuri", for example?

Well, it's obviously the sore thumb sticking out, but that doesn't mean 
we "otta" make it two sore thumbs! =8^)

In any case, just because I'm supporting what may be a compromise doesn't 
necessarily mean I support the convention one side was arguing, as the 
second-person "your" (whether singular or plural) would indicate.  I'm 
more or less neutral on that, personally, only supporting it here as a 
way to work with the people for whom it seems to be an issue.  
Personally, if it comes down to the "It's a list of flags, called 
'RESTRICT' only due to historical reasons" argument, so be it.

(Said as a user who contributed one live ebuild now in the tree, and uses 
a few others.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




  reply	other threads:[~2008-08-03 13:04 UTC|newest]

Thread overview: 28+ 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
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 [this message]
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

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=pan.2008.08.03.13.04.33@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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