1 |
On 11:11 Sat 13 Oct , Torsten Veller wrote: |
2 |
> * Donnie Berkholz <dberkholz@g.o>: |
3 |
> > On 10:44 Sat 13 Oct , Torsten Veller wrote: |
4 |
> > > * Donnie Berkholz <dberkholz@g.o>: |
5 |
> > > > python_mod_optimize() and python_mod_cleanup() already tag ROOT on, |
6 |
> > > |
7 |
> > > python_mod_optimize() does not. |
8 |
> > |
9 |
> > Mine does: |
10 |
> > |
11 |
> > python_mod_optimize() { |
12 |
> > local myroot |
13 |
> > # strip trailing slash |
14 |
> > myroot="${ROOT%/}" |
15 |
> > |
16 |
> > ... |
17 |
> > |
18 |
> > ebegin "Byte compiling python modules for python-${PYVER} .." |
19 |
> python${PYVER} ${myroot}/usr/$(get_libdir)/python${PYVER}/compileall.py ${compileopts} $@ |
20 |
> python${PYVER} -O ${myroot}/usr/$(get_libdir)/python${PYVER}/compileall.py ${compileopts} $@ |
21 |
> > eend $? |
22 |
> > } |
23 |
> |
24 |
> No. The arguments of python_mod_optimize are just passed to the ROOTed compileall.py. |
25 |
|
26 |
It took me about five minutes to figure out what you meant: this means |
27 |
that the filenames do not get passed with ROOT prepended to them, so |
28 |
compileall.py in ROOT compiles the files outside of ROOT. |
29 |
|
30 |
Thanks, |
31 |
Donnie |
32 |
-- |
33 |
gentoo-dev@g.o mailing list |