The ESVN_BOOTSTRAP and EGIT_BOOTSTRAP variables seems to be used only to call boostrap/autogen scripts (instead of using eautoreconf).
Considering that boostrap/autogen scripts are usually a very nasty idea, I'd like for use of the two variable to raise a QA Warning.
If further steps are needed after the source fetching through subversion/git, it should happen in src_unpack as we do for every other thing in other ebuilds and eclasses.
(Similarly, ESVN_PATCHES and EGIT_PATCHES should be deprecated too, if we really want to make that change, we could just let subversion and git eclasses inherit base.eclass and use the already-present PATCHES array, instead of reinventing the wheel).
You're assuming that bootstrap scripts can be replaced by calling eautoreconf. This often isn't the case.
No I'm not.
> If further steps are needed after the source fetching through subversion/git,
> it should happen in src_unpack as we do for every other thing in other ebuilds
> and eclasses.
Sure. And that thing is often "run the autogen / bootstrap" script. So you might as well just use the *_BOOTSTRAP var.
Any input from anyone on how they would like to proceed with this bug? Its been stalled for quite some time now.