| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Zac Medico schrieb: |
| 5 |
> I chose "live" because I think it's easy for people to associate it |
| 6 |
> with "live ebuilds", which I believe is a common term used to refer |
| 7 |
> to ebuild that download live sources in src_unpack. What's in a name |
| 8 |
> though? I'll gladly use whatever name satisfies the most people. |
| 9 |
|
| 10 |
Why not rename "live" to something which makes more sense in the |
| 11 |
RESTRICT environment? Like the "constant-source" suggestion by Arfrever? |
| 12 |
Because for me 'RESTRICT="live"' reads like: "Live(-builds)" are not |
| 13 |
possible with this ebuild. |
| 14 |
|
| 15 |
Pushing random boolean flags in a variable, just because it already |
| 16 |
happens to be there, seems (for me) to be the wrongest possible |
| 17 |
approach. This would be quite similar to: We want to store the ebuild's |
| 18 |
author in the ebuild... Hmm - we would need an additional string |
| 19 |
variable for this ... Come - let's use the IUSE variable - there are |
| 20 |
already strings in there (perhaps add an '@' before the author so we can |
| 21 |
parse it). |
| 22 |
|
| 23 |
Just my 2ct, |
| 24 |
René |
| 25 |
-----BEGIN PGP SIGNATURE----- |
| 26 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 27 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 28 |
|
| 29 |
iEYEARECAAYFAkiU6LkACgkQ4UOg/zhYFuBrVgCfRs/69DxNBy3TN0fsLr20gURW |
| 30 |
BxMAnie5SoBzbKN6n2oMhOJvMywV1ydf |
| 31 |
=aOCm |
| 32 |
-----END PGP SIGNATURE----- |
Archives