1 |
Dnia 2014-05-05, o godz. 17:26:14 |
2 |
hasufell <hasufell@g.o> napisał(a): |
3 |
|
4 |
> Michał Górny: |
5 |
> > This was planned for a while. The concept of 'best' and 'native' that |
6 |
> > are not always the same ABI is confusing and mostly unnecessary. |
7 |
> > Additionally, we prefer people using multilib-minimal phases rather than |
8 |
> > multilib_for* functions. |
9 |
> > --- |
10 |
> > eclass/multilib-build.eclass | 3 +++ |
11 |
> > 1 file changed, 3 insertions(+) |
12 |
> > |
13 |
> > diff --git a/eclass/multilib-build.eclass b/eclass/multilib-build.eclass |
14 |
> > index 4a87af6..de6c27b 100644 |
15 |
> > --- a/eclass/multilib-build.eclass |
16 |
> > +++ b/eclass/multilib-build.eclass |
17 |
> > @@ -210,6 +210,9 @@ multilib_parallel_foreach_abi() { |
18 |
> > multilib_for_best_abi() { |
19 |
> > debug-print-function ${FUNCNAME} "${@}" |
20 |
> > |
21 |
> > + eqawarn "QA warning: multilib_for_best_abi() function is deprecated and should" |
22 |
> > + eqawarn "not be used. The multilib_is_native_abi() check may be used instead." |
23 |
> > + |
24 |
> > local MULTIBUILD_VARIANTS=( $(multilib_get_enabled_abi_pairs) ) |
25 |
> > |
26 |
> > multibuild_for_best_variant _multilib_multibuild_wrapper "${@}" |
27 |
> > |
28 |
> |
29 |
> I wonder if it makes sense to add a repoman warning for these kind of |
30 |
> deprecations? Not sure if many people read the post-emerge output. By |
31 |
> experience, not so many. |
32 |
|
33 |
I was thinking about that wrt multilib_build_binaries but it seems that |
34 |
in current repoman code, the check for each function is treated |
35 |
as a separate test. I'd rather wait till someone adds a single test |
36 |
with a list for deprecated functions instead :). |
37 |
|
38 |
-- |
39 |
Best regards, |
40 |
Michał Górny |