Re: [gentoo-dev] Calling unknown commands in an ebuild

[Peter Volkov <pva@gentoo.org>]

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

В Вск, 07/02/2010 в 21:24 -0500, Mike Frysinger пишет:
> it might also be useful to add a default epatch() to the initial env that 
> would be clobbered when the inherit occurred.
> 	epatch() { die "you need to inherit eutils.eclass to use epatch" ; }

After fixing breakage that was introduced by dropping inherit eutils
from distutils.eclass I think we must have such thing. But one function
just covers most common case while we need to cover all cases. What
about pregenerating env file with script like in attachment?

$ awk -f generate-die-eclass-env /usr/portage/eclass/*.eclass

I guess it's possible to generate such env file on server side and make
portage use it if file exists... Opinions?

-- 
Peter.

[-- Attachment #2: generate-die-eclass-env --]
[-- Type: application/x-awk, Size: 338 bytes --]