1 |
В Вск, 07/02/2010 в 21:24 -0500, Mike Frysinger пишет: |
2 |
> it might also be useful to add a default epatch() to the initial env that |
3 |
> would be clobbered when the inherit occurred. |
4 |
> epatch() { die "you need to inherit eutils.eclass to use epatch" ; } |
5 |
|
6 |
After fixing breakage that was introduced by dropping inherit eutils |
7 |
from distutils.eclass I think we must have such thing. But one function |
8 |
just covers most common case while we need to cover all cases. What |
9 |
about pregenerating env file with script like in attachment? |
10 |
|
11 |
$ awk -f generate-die-eclass-env /usr/portage/eclass/*.eclass |
12 |
|
13 |
I guess it's possible to generate such env file on server side and make |
14 |
portage use it if file exists... Opinions? |
15 |
|
16 |
-- |
17 |
Peter. |