* Peter Eisentraut <[EMAIL PROTECTED]> [011106 20:01]:
> D'Arcy J.M. Cain writes:
> > I have a change I would like to discuss.  It doesn't change the code
> > base, only the build system.  The patches I would like to commit follow
> > this text.  The only thing it does is create a config option to bytecode
> > compile the Python modules.
> We've seen such a patch before, but I'm still not convinced it works.
> According to my knowledge, the pre-compiled bytecode files need to be
> created after the source files have been installed in their final
> location, because the file name and timestamp is encoded in the compiled
> file (it's sort of used as a cache file).  While this can be accomplished
> with a different patch, it wouldn't really work when DESTDIR is used
> because you'd create a "dead" cache file.  In a sense, this operation is
> like running ldconfig -- it's outside the scope of the build system.
> Package managers typically put it in the "post install" section.

Do you have a reference for this?  I tried looking for one but the only
thing I could find was http://www.python.org/doc/1.6/dist/built-dist.html
which suggests to me that they can be compiled before shipping which of
course certainly involves moving them.  In any case NetBSD does this
patch before building and everything works there.

D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to