In pre-EAPI-2, src_unpack phase was the most logical phase to be provided by
SCM eclasses, thus classes has been set up to export ${ECLASS}_src_unpack.
This phase in most (if not all) SCM eclasses provided:
- unpack functionality - fetch and store in ${DISTDIR}
- bootstrap functionality - either
> On Thu, 24 Sep 2009, Maciej Mrozowski wrote:
> Because SCM bootstrap is either not used at all, or used very
> rarely, there's suggestion to:
> - either drop it
> - or (preferably) to make SCM eclasses export src_prepare only on
> specific request
> - or to make it easier - to not export i
On Thursday 24 of September 2009 08:32:53 Ulrich Mueller wrote:
It's all about making live <-> tagged ebuild synchronization easier.
Currently
> Not a good idea, IMHO. In pre-EAPI-2, the SCM eclasses shadow
> src_unpack of base.eclass, so also no autopatching of base.eclass
> takes place. If we n
On 15:46 Thu 24 Sep , Maciej Mrozowski wrote:
> Because autopatcher makes it able to specify patches that are version
> independent (same patches for live and tagged ebuilds), while SCM
> patching/bootstrapping may be used for some specific cases (I haven't seen
> any
> yet personally, henc
