Hi Laszlo! (And hi Cc'ed ceph-dev.) As you probably know, the Ceph project tries to provide debs for Debian lenny, squeeze and sid, and Ubuntu lucid, maverick and natty. We're starting to add Python bindings to libceph, librados etc, and ran into a case where not 100% sure how to handle. That is, how should we package e.g. rados.py so that the packaging works across as many releases as we can? There is the Debian Python Policy, but that usually only documents the current best behavior; how do we target more than squeeze/sid? http://www.debian.org/doc/packaging-manuals/python-policy/ e.g. should we use python-central, python-support, put the files ourselves into /usr/lib/pythonX.Y/dist-packages (or site-packages, for <2.6), or what? (I heard Sage was perhaps willing to drop some of the oldest releases, if this proves insurmountable to do with just one style of packaging. Our internal needs may dictate that we must support some older versions, but I think those setups are going to need a virtualenv anyway, soon..) Any guidance you can provide would be very welcome. Thanks! -- :(){ :|:&};: -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
