On Sat, Oct 17, 2015 at 8:52 AM, Ulrich Mueller <[email protected]> wrote: > > That eapply_user is called can be enforced by repoman, or by a QA > warning. >
I hate to reply again on the same topic, but how would repoman even know whether eapply_user will always get called? Isn't that equivalent to the halting problem? 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. -- Rich
