1 |
Michał Górny: |
2 |
> This was planned for a while. The concept of 'best' and 'native' that |
3 |
> are not always the same ABI is confusing and mostly unnecessary. |
4 |
> Additionally, we prefer people using multilib-minimal phases rather than |
5 |
> multilib_for* functions. |
6 |
> --- |
7 |
> eclass/multilib-build.eclass | 3 +++ |
8 |
> 1 file changed, 3 insertions(+) |
9 |
> |
10 |
> diff --git a/eclass/multilib-build.eclass b/eclass/multilib-build.eclass |
11 |
> index 4a87af6..de6c27b 100644 |
12 |
> --- a/eclass/multilib-build.eclass |
13 |
> +++ b/eclass/multilib-build.eclass |
14 |
> @@ -210,6 +210,9 @@ multilib_parallel_foreach_abi() { |
15 |
> multilib_for_best_abi() { |
16 |
> debug-print-function ${FUNCNAME} "${@}" |
17 |
> |
18 |
> + eqawarn "QA warning: multilib_for_best_abi() function is deprecated and should" |
19 |
> + eqawarn "not be used. The multilib_is_native_abi() check may be used instead." |
20 |
> + |
21 |
> local MULTIBUILD_VARIANTS=( $(multilib_get_enabled_abi_pairs) ) |
22 |
> |
23 |
> multibuild_for_best_variant _multilib_multibuild_wrapper "${@}" |
24 |
> |
25 |
|
26 |
I wonder if it makes sense to add a repoman warning for these kind of |
27 |
deprecations? Not sure if many people read the post-emerge output. By |
28 |
experience, not so many. |