| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Zac Medico schrieb: |
| 5 |
> Well, RESTRICT has long since evolved into a rather generic set of |
| 6 |
> boolean flags and it's quite useful as such. I don't see any need |
| 7 |
> for artificial limitations on what types of flags go there. |
| 8 |
|
| 9 |
For you it is just "one variable amongst others" - and you really don't |
| 10 |
care about the relation between its name and its content. But perhaps |
| 11 |
just for the sake of easier understanding of ebuilds, this relation |
| 12 |
should be kept. Otherwise you'll read in future documentation: "The name |
| 13 |
is just for historical reasons and does not reflect the content." -- And |
| 14 |
this is nearly always a stumbling block for the non-experienced. |
| 15 |
|
| 16 |
Perhaps in a later EAPI RESTRICT might be renamed to something like |
| 17 |
FLAGS - and then can really be used as a pool of flags. |
| 18 |
-----BEGIN PGP SIGNATURE----- |
| 19 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 20 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 21 |
|
| 22 |
iEYEARECAAYFAkiU8p8ACgkQ4UOg/zhYFuBeSQCfaPCuNXk99lde0lvriV1GFDMu |
| 23 |
6FgAnRetvxI1uHWnZH2lizEiTIB+7IOC |
| 24 |
=wStZ |
| 25 |
-----END PGP SIGNATURE----- |
Archives