| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
René 'Necoro' Neumann wrote: |
| 5 |
> Zac Medico schrieb: |
| 6 |
>> I chose "live" because I think it's easy for people to associate it |
| 7 |
>> with "live ebuilds", which I believe is a common term used to refer |
| 8 |
>> to ebuild that download live sources in src_unpack. What's in a name |
| 9 |
>> though? I'll gladly use whatever name satisfies the most people. |
| 10 |
> |
| 11 |
> Why not rename "live" to something which makes more sense in the |
| 12 |
> RESTRICT environment? Like the "constant-source" suggestion by Arfrever? |
| 13 |
> Because for me 'RESTRICT="live"' reads like: "Live(-builds)" are not |
| 14 |
> possible with this ebuild. |
| 15 |
|
| 16 |
I'm pretty flexible on the name but like I said before I think the |
| 17 |
convention you're referring to is pretty worthless. |
| 18 |
|
| 19 |
> Pushing random boolean flags in a variable, just because it already |
| 20 |
> happens to be there, seems (for me) to be the wrongest possible |
| 21 |
> approach. This would be quite similar to: We want to store the ebuild's |
| 22 |
> author in the ebuild... Hmm - we would need an additional string |
| 23 |
> variable for this ... Come - let's use the IUSE variable - there are |
| 24 |
> already strings in there (perhaps add an '@' before the author so we can |
| 25 |
> parse it). |
| 26 |
> |
| 27 |
> Just my 2ct, |
| 28 |
> René |
| 29 |
|
| 30 |
Well, RESTRICT has long since evolved into a rather generic set of |
| 31 |
boolean flags and it's quite useful as such. I don't see any need |
| 32 |
for artificial limitations on what types of flags go there. |
| 33 |
|
| 34 |
Zac |
| 35 |
-----BEGIN PGP SIGNATURE----- |
| 36 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 37 |
|
| 38 |
iEYEARECAAYFAkiU7l8ACgkQ/ejvha5XGaP0MwCfR/zaBv0afq019vOOjuaEzdAJ |
| 39 |
FhcAnRsedFGVQY9gyxJbadCqWEBLbfrZ |
| 40 |
=2gKy |
| 41 |
-----END PGP SIGNATURE----- |
Archives