| 1 |
On 09/27/2012 09:49 AM, Ulrich Mueller wrote: |
| 2 |
> As far as I can see, only the definition of the usex function must be |
| 3 |
> disabled. Please review the patch included below. |
| 4 |
> |
| 5 |
> Ulrich |
| 6 |
> |
| 7 |
> --- eutils.eclass 15 Sep 2012 16:16:53 -0000 1.403 |
| 8 |
> +++ eutils.eclass 27 Sep 2012 16:45:14 -0000 |
| 9 |
> @@ -1373,7 +1373,9 @@ |
| 10 |
> # @DESCRIPTION: |
| 11 |
> # If USE flag is set, echo [true output][true suffix] (defaults to "yes"), |
| 12 |
> # otherwise echo [false output][false suffix] (defaults to "no"). |
| 13 |
> +if has "${EAPI:-0}" 0 1 2 3 4; then |
| 14 |
> usex() { use "$1" && echo "${2-yes}$4" || echo "${3-no}$5" ; } #382963 |
| 15 |
> +fi |
| 16 |
> |
| 17 |
> # @FUNCTION: prune_libtool_files |
| 18 |
> # @USAGE: [--all] |
| 19 |
> |
| 20 |
|
| 21 |
Looks good to me. |
| 22 |
|
| 23 |
It may not work for unofficial EAPIs that don't include usex, but I |
| 24 |
guess there's nothing we can do for those, and they can just be replaced |
| 25 |
with newer EAPIs that include usex. |
| 26 |
-- |
| 27 |
Thanks, |
| 28 |
Zac |
Archives