| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Joe Peterson wrote: |
| 5 |
> I'm not sure the "EBUILD_" in "EBUILD_FLAGS" would be necessary |
| 6 |
> (redundant?). Maybe even "OPTIONS" or "PROPERTIES" makes more sense. |
| 7 |
> In fact, "FLAGS" might be a little too generic, even? Worth a short |
| 8 |
> discussion. |
| 9 |
|
| 10 |
One potential issue with using a short generic name is the potential |
| 11 |
for variable name collisions. It's mainly an issue if we want to |
| 12 |
mark the variable readonly during normal ebuild phases. If the |
| 13 |
variable is marked readonly then bash will not allow that variable |
| 14 |
name to be used as either a global or a _local_ variable. Maybe it |
| 15 |
doesn't really matter though. |
| 16 |
|
| 17 |
Zac |
| 18 |
-----BEGIN PGP SIGNATURE----- |
| 19 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 20 |
|
| 21 |
iEYEARECAAYFAkiWKuYACgkQ/ejvha5XGaPdgQCfXyDdAPN22+Jn/szjD0zG99eH |
| 22 |
xqgAn28jCCmEOLoKfKSspbJbGskUwjtI |
| 23 |
=rDmY |
| 24 |
-----END PGP SIGNATURE----- |
Archives