[Distutils] Packaging: bdist_deb patches

David Lyon david.lyon at preisshare.net
Thu Jun 11 00:55:37 CEST 2009

On Wed, 10 Jun 2009 08:30:26 -0600, Zooko Wilcox-O'Hearn <zooko at zooko.com>
> I use stdeb for this purpose:
> http://pypi.python.org/pypi/stdeb
> For example, here is a buildbot which automatically builds a new .deb  
> from the Python source whenever a new patch is committed to the  
> revision control repository:
> http://allmydata.org/buildbot-pycryptopp/builders/linux-amd64-ubuntu- 
> hardy-yukyuk/builds/82/steps/stdeb/logs/stdio

That sounds excellent....

To my mind, that's what bdist_* and pypi need....

Not talking about anything contriversial or new or big....

But just better integration so that we can get a build of our
projects done more smoothly and uploaded to pypi on several
different python versions and platforms...

with the built in qa facilities that might already exist
to us.....

Maybe it is logical to discuss splitting bdist_* from
distutils. Given that there is so much platform specific
stuff in bdist_*. But then what does it leave distutils
as? "packageutils" ? 

I think there is some logical division between platform 
independant package definition issues (which I know 
certain people like working on - and that's good) and 
the package delivery side. (bdist)

The two seem fairly seperate to me. Yet they both make
up distutils.

Just following on and trying to clarify what other
people have put in the discussion pot...


More information about the Distutils-SIG mailing list