Re: [gentoo-dev] New eclass proposal: auto-export

[Maciej Mrozowski]

On Wednesday 22 of April 2009 15:35:37 Petteri Räty wrote:
> Here's an eclass proposal to wrap EXPORT_FUNCTIONS with auto detection
> of functions. This way all eclasses don't have to duplicate the EAPI
> detection code. If people find this useful, I will document it properly
> with eclass-manpages etc.

I like the idea, I'd have some feature request regarding it.

I'd like to have global eclass-wise EXPORT_FUNCTIONS variable introduced in 
ebuilds (functions and variables can have identical names, bash handles it) 
with list of allowed phases to export for all inherited eclasses.
It's needed in cases when eclass global scope is needed (for some setup for 
example, setting SLOT etc) but overriding phases is not desired.
Currently it seems to be needed to override every not needed phase with dummy

phase_function() {
	:
}

It means overriding all src_* phases if no ${S} is present.

With proposed solution, there would be for example:
in ebuild:

EXPORT_FUNCTIONS="pkg_setup pkg_postinst pkg_postrm"
inherit kde4-base
[...]

in eclasses there would be autoexport code

autoexport.eclass would need to be tweaked to export only those defined phases 
that are listed in EXPORT_FUNCTIONS if EXPORT_FUNCTIONS is not empty
That would disable overriding not wanted phases all way down (provided all 
eclasses all way down use autoexport that is).

-- 
regards
MM