| 1 |
On 10:44 Sat 13 Oct , Torsten Veller wrote: |
| 2 |
> * Donnie Berkholz <dberkholz@g.o>: |
| 3 |
> > python_mod_optimize() and python_mod_cleanup() already tag ROOT on, |
| 4 |
> |
| 5 |
> python_mod_optimize() does not. |
| 6 |
|
| 7 |
Mine does: |
| 8 |
|
| 9 |
python_mod_optimize() { |
| 10 |
local myroot |
| 11 |
# strip trailing slash |
| 12 |
myroot="${ROOT%/}" |
| 13 |
|
| 14 |
... |
| 15 |
|
| 16 |
ebegin "Byte compiling python modules for python-${PYVER} .." |
| 17 |
python${PYVER} ${myroot}/usr/$(get_libdir)/python${PYVER}/compileall.py ${c$ |
| 18 |
python${PYVER} -O ${myroot}/usr/$(get_libdir)/python${PYVER}/compileall.py $ |
| 19 |
eend $? |
| 20 |
} |
| 21 |
|
| 22 |
> > so for ROOT != / this is broken. |
| 23 |
> |
| 24 |
> But does python_mod_optimize do anything useful with ROOT !=/ and |
| 25 |
> cross-compilation? What if python versions differ? |
| 26 |
|
| 27 |
That's a good question, and it looks like python_version() could use a |
| 28 |
fix for ROOT != / on same-arch systems. On cross-compiled, it'll |
| 29 |
probably be more work and I'm not sure how to deal with it. |
| 30 |
|
| 31 |
Thanks, |
| 32 |
Donnie |
| 33 |
-- |
| 34 |
gentoo-dev@g.o mailing list |
Archives