On Sun, 18 Oct 2015 11:54:40 +0200
Ulrich Mueller <u...@gentoo.org> wrote:

> >>>>> On Sat, 17 Oct 2015, Rich Freeman wrote:  
> 
> > That would be another reason to have the PM do the check.  All it
> > has to do is set an internal flag when it is called, and then check
> > the flag before starting the next phase.  Then you can have as many
> > levels of conditionals and nested functions in eclasses as you want,
> > and the check still works.  
> 
> So the question is if we should add a sentence like the following to
> the spec:
> 
>     In EAPIs where it is supported, all ebuilds must run
>     \t{eapply\_user} in the \t{src\_prepare} phase.

How about:

    In EAPIs listed in table blah blah blah, \t{eapply\_user} must
    be called exactly once in the \t{src\_prepare} phase.

Which emphasizes that eclass or default may do it instead of ebuild.

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

Attachment: pgpro6aCEkY_T.pgp
Description: OpenPGP digital signature

Reply via email to