Excerpts from Dagobert Michelsen's message of Sun Jul 12 09:23:02 -0400 2009:
Hi Sebastian and Dago,

I put together a small patch (attached) for GAR to twiddle the
required bits for use of cswpycompile in an automatic fashion.  I
didn't make it happen implicitly, as after thinking more about the
changes I'll make to support automatic elisp handling, I didn't think
implicit was the right way to go here.

The patch will take any value of CSWPYCOMPILE to mean that
cswpycompile is added to SPKG_CLASSES, .pyc and .pyo files are
filtered from the merge by default, .py files are set to cswpycompile
in the prototype and CSWcswclassutils is added as a dependency.

If you're ok with the changes, I'll make the commit and document the
new variable.

> > EXTRA_PAX_ARGS = -s ',^.*/\(xcbgen/.*\.py\),.$(BUILD_PREFIX)/lib/ 
> > python/site-packages/\1,'
> > EXTRA_PAX_ARGS += -s ',^\.$(libdir)/python.*,,'

Dago: I didn't alter any of the PAX stuff for this patch, since it
didn't seem to be necessary...is this part of your recipe due to the
file relocation you're performing here?

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.

Attachment: autopy.patch
Description: Binary data

Attachment: signature.asc
Description: PGP signature

_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers

Reply via email to