On Tue, 2009-03-10 at 18:08 +0100, Fabian Groffen wrote:
> On 10-03-2009 17:34:45 +0100, Fabian Groffen wrote:
> > On 10-03-2009 17:17:00 +0100, Michael Haubenwallner wrote:
> > > Maybe indeed you're right, eprefixify is just an utility to help fixing
> > > package's code and should not be part of an EAPI.
> > 
> > I think I'll draft up a proposal tonight.
> 
> Please review my first shot at prefix.eclass

Hmm, 'use' in global scope?

Eventually, when one of EPREFIX/EROOT/ED is *unset*, set all of them,
because we for sure do not have prefix-portage then, user might have set
one of them by hand - somehow like:

        if [[ ${EPREFIX+yes}${EROOT+we}${ED+can} != "yeswecan" ]]; then
            export EPREFIX=""
            export EROOT=${ROOT}
            export ED=${D}
        fi

/haubi/
-- 
Michael Haubenwallner
Gentoo on a different level