1 |
On Tue, 2009-03-10 at 18:08 +0100, Fabian Groffen wrote: |
2 |
> On 10-03-2009 17:34:45 +0100, Fabian Groffen wrote: |
3 |
> > On 10-03-2009 17:17:00 +0100, Michael Haubenwallner wrote: |
4 |
> > > Maybe indeed you're right, eprefixify is just an utility to help fixing |
5 |
> > > package's code and should not be part of an EAPI. |
6 |
> > |
7 |
> > I think I'll draft up a proposal tonight. |
8 |
> |
9 |
> Please review my first shot at prefix.eclass |
10 |
|
11 |
Hmm, 'use' in global scope? |
12 |
|
13 |
Eventually, when one of EPREFIX/EROOT/ED is *unset*, set all of them, |
14 |
because we for sure do not have prefix-portage then, user might have set |
15 |
one of them by hand - somehow like: |
16 |
|
17 |
if [[ ${EPREFIX+yes}${EROOT+we}${ED+can} != "yeswecan" ]]; then |
18 |
export EPREFIX="" |
19 |
export EROOT=${ROOT} |
20 |
export ED=${D} |
21 |
fi |
22 |
|
23 |
/haubi/ |
24 |
-- |
25 |
Michael Haubenwallner |
26 |
Gentoo on a different level |