Hi there, I have just built and uploaded to Google Code the following packages of pygr-0.8.0.alpha2: - source tarball; - binary tarballs for Linux/x86 and Linux/amd64, Python 2.5; - executable installer for Win32, Python 2.5; - EGG versions of all three aforementioned binary packages.
Let me know if you think any other packages should be built (IMHO it would make sense to also build Linux packages for Python 2.4, since many distros still use it as default - and of course we could use some OS X packages), or even better - sent me ones you've built yourselves :-) Some notes on the procedure (FYI, I used setup in setuptools mode, with setuptools-git installed): - "setup sdist" doesn't include Pyrex-built .c files. The easiest way to address this will be to add those files to the repository - they do not change that frequently and in setuptools mode, Python will automatically rebuild them if .pyx files are newer; what needs to be checked is (note to mostly self) how this would work in distutils mode. Alternatively, we need to work on a manifest template; - "setup bdist" preserves Python's directory structure of the build host (which explains why my Linux/amd64 package uses /usr/local and the Linux/x86 one - /usr), raising the question of whether such packages could be used (without manual shuffling of files) on systems on which appropriate versions of Python are installed elsewhere. Could anyone try this? Anyhow, AFAIK the solution here is to use eggs, if possible (IIRC you need setuptools/easy_install for that). As usual, all feedback is welcome. -- MS --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
