| 1 |
On Sun, 18 Oct 2015 11:54:40 +0200 |
| 2 |
Ulrich Mueller <ulm@g.o> wrote: |
| 3 |
|
| 4 |
> >>>>> On Sat, 17 Oct 2015, Rich Freeman wrote: |
| 5 |
> |
| 6 |
> > That would be another reason to have the PM do the check. All it |
| 7 |
> > has to do is set an internal flag when it is called, and then check |
| 8 |
> > the flag before starting the next phase. Then you can have as many |
| 9 |
> > levels of conditionals and nested functions in eclasses as you want, |
| 10 |
> > and the check still works. |
| 11 |
> |
| 12 |
> So the question is if we should add a sentence like the following to |
| 13 |
> the spec: |
| 14 |
> |
| 15 |
> In EAPIs where it is supported, all ebuilds must run |
| 16 |
> \t{eapply\_user} in the \t{src\_prepare} phase. |
| 17 |
|
| 18 |
How about: |
| 19 |
|
| 20 |
In EAPIs listed in table blah blah blah, \t{eapply\_user} must |
| 21 |
be called exactly once in the \t{src\_prepare} phase. |
| 22 |
|
| 23 |
Which emphasizes that eclass or default may do it instead of ebuild. |
| 24 |
|
| 25 |
-- |
| 26 |
Best regards, |
| 27 |
Michał Górny |
| 28 |
<http://dev.gentoo.org/~mgorny/> |
Archives