[gentoo-dev] Re: [RFC] Dropping (or enabling only on request) bootstrap from SCM eclasses

[Ryan Hill <dirtyepic@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]

On Thu, 24 Sep 2009 03:39:26 +0200
Maciej Mrozowski <reavertm@poczta.fm> wrote:

> And this is the problem (some people may be even unaware of it).
> In pre EAPI-2 it was sufficient to do the following in live ebuilds:
> 
> inherit ${some_eclass} ${scm_eclass}
> 
> ${scm_eclass} inherited as last one, would just shadow src_unpack, providing 
> what we want.

Oogh, no.  Relying on ordering of the inherit line is never a good idea.  If
you need to call scm_src_unpack, call scm_src_unpack.

> 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 it at all - thus making it required for 
> developer to intentionally invoke ${ECLASS}_src_prepare if bootstrapping is 
> required.

Why not do number 3 but call it ${ECLASS}_bootstrap?  If people need it they
can call it from src_prepare.


-- 
fonts,                             Character is what you are in the dark.
gcc-porting,
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]