| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Santiago M. Mola wrote: |
| 5 |
> If you're just dealing with the default phases, it's not too hard to |
| 6 |
> say in advance the exact command that will be executed. |
| 7 |
|
| 8 |
If that's the case, why go so far as to define three new variables and |
| 9 |
potentially put them out in the main variable area? If we've got |
| 10 |
default_src_compile defined, we could do the following: |
| 11 |
|
| 12 |
src_compile() { |
| 13 |
default_conf="$(use_with blah) |
| 14 |
$(use_enable flibble)" |
| 15 |
default_src_compile |
| 16 |
} |
| 17 |
|
| 18 |
It then doesn't require *any* additional changes (except maybe to give |
| 19 |
default_src_compile a well known variable name like $default_conf). |
| 20 |
This is then only a single variable, and no more difficult to remember |
| 21 |
than some of the eutils function names, and just as easy to look up. |
| 22 |
|
| 23 |
It seems to allow the maximum flexibility, with the minimum changes to |
| 24 |
package managers (assuming the defaults get into EAPI-2). |
| 25 |
|
| 26 |
Mike 5:) |
| 27 |
-----BEGIN PGP SIGNATURE----- |
| 28 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 29 |
|
| 30 |
iEYEARECAAYFAkjE8vsACgkQu7rWomwgFXomRACgnvJZPSWEaSls4Fd+cy3T1cF5 |
| 31 |
UWQAoJ9fnZ82v5r2S/oz6GBo5Ot8iC9a |
| 32 |
=pgRO |
| 33 |
-----END PGP SIGNATURE----- |
Archives