1 |
Hi, |
2 |
|
3 |
On Sat, 30 Jul 2016 12:34:07 +0300 Andrew Savchenko wrote: |
4 |
> On Sat, 30 Jul 2016 07:37:08 +0200 Michał Górny wrote: |
5 |
> > > @@ -116,7 +123,8 @@ ESVN_PROJECT="${ESVN_PROJECT:-${PN/-svn}}" |
6 |
> > > |
7 |
> > > # @ECLASS-VARIABLE: ESVN_BOOTSTRAP |
8 |
> > > # @DESCRIPTION: |
9 |
> > > -# bootstrap script or command like autogen.sh or etc.. |
10 |
> > > +# Bootstrap script or command like autogen.sh or etc.. |
11 |
> > > +# Removed in EAPI 6 and later. |
12 |
> > > ESVN_BOOTSTRAP="${ESVN_BOOTSTRAP:-}" |
13 |
> > > |
14 |
> > > # @ECLASS-VARIABLE: ESVN_PATCHES |
15 |
> > > @@ -127,6 +135,8 @@ ESVN_BOOTSTRAP="${ESVN_BOOTSTRAP:-}" |
16 |
> > > # |
17 |
> > > # Patches are searched both in ${PWD} and ${FILESDIR}, if not found in either |
18 |
> > > # location, the installation dies. |
19 |
> > > +# |
20 |
> > > +# Removed in EAPI 6 and later, use PATCHES instead. |
21 |
> > > ESVN_PATCHES="${ESVN_PATCHES:-}" |
22 |
> > |
23 |
> > It would be a good idea to check if the variables are set and die if |
24 |
> > they are, so people don't accidentally use them. |
25 |
> |
26 |
> Impossible to implement. These variables (as well as all other |
27 |
> ESVN_* variables) are usually set after subversion eclass is |
28 |
> inherited. And even if I'll duplicate this check in all available |
29 |
> functions (which is ridiculous by itself), it still will not help, |
30 |
> since several functions are removed from EAPI 6 and people may |
31 |
> rely on default behaviour of src_prepare() alone. |
32 |
> |
33 |
> > > # @ECLASS-VARIABLE: ESVN_RESTRICT |
34 |
> > > @@ -355,7 +365,10 @@ subversion_fetch() { |
35 |
> > > # @FUNCTION: subversion_bootstrap |
36 |
> > > # @DESCRIPTION: |
37 |
> > > # Apply patches in ${ESVN_PATCHES} and run ${ESVN_BOOTSTRAP} if specified. |
38 |
> > > +# Removed in EAPI 6 and later. |
39 |
> > > subversion_bootstrap() { |
40 |
> > > + has "${EAPI:-0}" 6 && die "${FUNCNAME[1]} is removed from subversion.eclass in EAPI 6 and later" |
41 |
> > > + |
42 |
> > |
43 |
> > Reverse the logic. This will require updating in every EAPI while it is |
44 |
> > rather unlikely the next EAPIs will return to previous behavior. |
45 |
> |
46 |
> Done. |
47 |
|
48 |
No further comments for a week => in the tree now. |
49 |
Thank you for review. |
50 |
|
51 |
Best regards, |
52 |
Andrew Savchenko |