PyPi Packages

Introduction

This archive has alpha-quality RPM packages built from the Python Package Index. Currently these are here largely for the early adopters to test out and discuss a long-term distribution package repository, including Debian packages.

Note: These packages are currently here for testing purposes only and may not play well with future packages that are built. In particular, versions and names may change or stay the same, requiring manual intervention to install newly built packages.

The Packages

The packages currently do not work with "yum" as a repository. The repository files are there, but on Fedora 10 and CentOS 5 they are causing yum to exit with a cryptic message I have not yet resolved. CentOS 4 *MAY* work as a yum repository.

The repositories are available at:

• CentOS
• Fedora

Package Mainainter

If you maintain a package on the cheeseshop (http://pypi.python.org/pypi), there are a few things you should know about this repository:

• You can see the build output of all packages at: http://10tons.tummy.com/pypi-output/
• Currently the builds are not automated. This is one of the first things I want to fix, but I will need to set up a secure way of rebuilding packages (so that one package can't compromise another, for example).
• The current packages were built with a 30 or 60 second time limit on the build. Some packages, if they looked like they were going well and just died, may have died because of the time limit. This time limit will probably be extended in the future.
• The packages are built basically just by doing "python setup.py bdist_rpm". There are some base set of packages installed on the system, but currently it doesn't do anything about installing dependencies that packages need which are not currently installed. We will probably need a way to specify this, on a per-distribution basis possibly, for both building and installing. I would like to have some community discussion on this.
• I rely on your source distribution being available either on the pypi.python.org machine (via the "python setup.py upload" command), or that the download link in PyPI point directly at a tar or zip file (.tar, .tar.gz, .tar.bz2, .tgz, .zip extensions). If your download link points at a generic download landing page, my programs can't find your code. I'm open to discussion on this, but in discussions I've had so far I've had no objections to the requirement that the source be on the pypi server.
• I'm hoping that package maintainers and I can work together to get maintainers the information they need to tweak their packages so that the build system can do the right thing without too many special cases on a package-by-package basis.

I appreciate any review and thoughts you have. Feel free to either discuss it on the python mailing list or via e-mail to jafo-community@tummy.com