1 |
El dom, 30-09-2012 a las 10:58 +0200, Fabian Groffen escribió: |
2 |
> On 30-09-2012 10:31:17 +0200, Pacho Ramos wrote: |
3 |
> > > > Personally, I usually run: |
4 |
> > > > - python_clean_py-compile_files -> Clean py-compile files to disable |
5 |
> > > > byte-compilation allowing us to drop all various ways of doing this that |
6 |
> > > > were living in the tree some time ago. |
7 |
> > > |
8 |
> > > Hmm, what's the problem with compiling them? Do you mean some case when |
9 |
> > > the results of the compilation are different from the way done |
10 |
> > > by the eclass? |
11 |
> > > |
12 |
> > |
13 |
> > Well, if I don't misremember, we currently prefer to compile them at |
14 |
> > postinst phase instead of during src_compile, but maybe this is no |
15 |
> > longer needed (no idea :( ) |
16 |
> |
17 |
> The files are indeed cache, and should be generated on the system that |
18 |
> installs the files, not the system that builds them. They are currently |
19 |
> outside of VDB. pyc files store the path to the original files, so |
20 |
> generating in ${ROOT} yields in wrong paths. Python sometimes |
21 |
> regenerates the files when it runs. It may as well just ignore them |
22 |
> (since they are newer but non-matching, unclear to me). In the worst |
23 |
> case it returns "Bad marshalling data". |
24 |
> |
25 |
> |
26 |
|
27 |
Then, I guess having such function would still be useful :) Thanks for |
28 |
the info |