1 |
Dnia 29 listopada 2015 13:24:43 CET, Justin Lecher <jlec@g.o> napisał(a): |
2 |
>Signed-off-by: Justin Lecher <jlec@g.o> |
3 |
>--- |
4 |
> eclass/virtualx.eclass | 17 ++++++++++++++++- |
5 |
> 1 file changed, 16 insertions(+), 1 deletion(-) |
6 |
> |
7 |
>diff --git a/eclass/virtualx.eclass b/eclass/virtualx.eclass |
8 |
>index bdecda6..344cd63 100644 |
9 |
>--- a/eclass/virtualx.eclass |
10 |
>+++ b/eclass/virtualx.eclass |
11 |
>@@ -22,7 +22,7 @@ case "${EAPI:-0}" in |
12 |
> ;; |
13 |
> esac |
14 |
> |
15 |
>-inherit eutils |
16 |
>+[[ ${EAPI} == [2345] ]] && inherit eutils |
17 |
> |
18 |
> # @ECLASS-VARIABLE: VIRTUALX_REQUIRED |
19 |
> # @DESCRIPTION: |
20 |
>@@ -58,6 +58,8 @@ case ${VIRTUALX_REQUIRED} in |
21 |
> RDEPEND="" |
22 |
> ;; |
23 |
> optional|tests) |
24 |
>+ [[ ${EAPI} == [2345] ]] \ |
25 |
>+ || die 'Values "optional" and "tests" for VIRTUALX_REQUIRED are |
26 |
>banned in EAPI > 5' |
27 |
> # deprecated section YAY. |
28 |
> eqawarn "VIRTUALX_REQUIRED=optional and VIRTUALX_REQUIRED=tests are |
29 |
>deprecated." |
30 |
> eqawarn "You can drop the variable definition completely from |
31 |
>ebuild," |
32 |
>@@ -89,8 +91,12 @@ esac |
33 |
> virtualmake() { |
34 |
> debug-print-function ${FUNCNAME} "$@" |
35 |
> |
36 |
>+ [[ ${EAPI} == [2345] ]] \ |
37 |
>+ || die "${FUNCNAME} is unsupported in EAPI > 5, please use virtx" |
38 |
>+ |
39 |
> # backcompat for maketype |
40 |
> if [[ -n ${maketype} ]]; then |
41 |
>+ [[ ${EAPI} == [2345] ]] || die "maketype is banned in EAPI > 5" |
42 |
> eqawarn "ebuild is exporting \$maketype=${maketype}" |
43 |
> eqawarn "Ebuild should be migrated to use |
44 |
>VIRTUALX_COMMAND=${maketype} instead." |
45 |
|
46 |
Here's one more reference to deprecated API. |
47 |
|
48 |
> eqawarn "Setting VIRTUALX_COMMAND to \$maketype conveniently for |
49 |
>now." |
50 |
>@@ -204,6 +210,9 @@ virtx() { |
51 |
> Xmake() { |
52 |
> debug-print-function ${FUNCNAME} "$@" |
53 |
> |
54 |
>+ [[ ${EAPI} == [2345] ]] \ |
55 |
>+ || die "${FUNCNAME} is unsupported in EAPI > 5, please use 'virtx |
56 |
>emake -j1 ....'" |
57 |
>+ |
58 |
> eqawarn "you should not execute make directly" |
59 |
> eqawarn "rather execute Xemake -j1 if you have issues with parallel |
60 |
>make" |
61 |
> VIRTUALX_COMMAND="emake -j1" virtualmake "$@" |
62 |
>@@ -215,6 +224,9 @@ Xmake() { |
63 |
> Xemake() { |
64 |
> debug-print-function ${FUNCNAME} "$@" |
65 |
> |
66 |
>+ [[ ${EAPI} == [2345] ]] \ |
67 |
>+ || die "${FUNCNAME} is unsupported in EAPI > 5, please use 'virtx |
68 |
>emake ....'" |
69 |
>+ |
70 |
> VIRTUALX_COMMAND="emake" virtualmake "$@" |
71 |
> } |
72 |
> |
73 |
>@@ -224,6 +236,9 @@ Xemake() { |
74 |
> Xeconf() { |
75 |
> debug-print-function ${FUNCNAME} "$@" |
76 |
> |
77 |
>+ [[ ${EAPI} == [2345] ]] \ |
78 |
>+ || die "${FUNCNAME} is unsupported in EAPI > 5, please use 'virtx |
79 |
>econf ....'" |
80 |
>+ |
81 |
> VIRTUALX_COMMAND="econf" virtualmake "$@" |
82 |
> } |
83 |
> |
84 |
|
85 |
-- |
86 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |