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

René 'Necoro' Neumann wrote:
> 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.

I'm pretty flexible on the name but like I said before I think the
convention you're referring to is pretty worthless.

> 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é

Well, RESTRICT has long since evolved into a rather generic set of
boolean flags and it's quite useful as such. I don't see any need
for artificial limitations on what types of flags go there.

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkiU7l8ACgkQ/ejvha5XGaP0MwCfR/zaBv0afq019vOOjuaEzdAJ
FhcAnRsedFGVQY9gyxJbadCqWEBLbfrZ
=2gKy
-----END PGP SIGNATURE-----