On Sun, 30 Sep 2012 10:58:06 +0200 Fabian Groffen <grob...@gentoo.org> wrote:
> On 30-09-2012 10:31:17 +0200, Pacho Ramos wrote:
> > > > Personally, I usually run:
> > > > - python_clean_py-compile_files -> Clean py-compile files to disable
> > > > byte-compilation allowing us to drop all various ways of doing this that
> > > > were living in the tree some time ago.
> > >
> > > Hmm, what's the problem with compiling them? Do you mean some case when
> > > the results of the compilation are different from the way done
> > > by the eclass?
> > >
> >
> > Well, if I don't misremember, we currently prefer to compile them at
> > postinst phase instead of during src_compile, but maybe this is no
> > longer needed (no idea :( )
>
> The files are indeed cache, and should be generated on the system that
> installs the files, not the system that builds them. They are currently
> outside of VDB. pyc files store the path to the original files, so
> generating in ${ROOT} yields in wrong paths. Python sometimes
> regenerates the files when it runs. It may as well just ignore them
> (since they are newer but non-matching, unclear to me). In the worst
> case it returns "Bad marshalling data".
I'm afraid you are wrong here.
I've just tested an ebuild using distutils (flaggie) and autotools
(pygobject) and both install .pyc files with correct paths (i.e. with
DESTDIR stripped).
--
Best regards,
Michał Górny
signature.asc
Description: PGP signature
