On Wed, Jan 28, 2009 at 14:07, Barry Warsaw <barry@python.org> wrote:
In my ideal world, I would make a release by tagging my release in whatever vcs I'm using, then I would tell cheeseshop, "hey I just released version 3.1 and it is here" where "here" means whatever native vcs syntax points to the revision I just released. Then PyPI would do the "coagulation" into distribution formats and distribute it amongst its worldwide mirrors, all automatically.
I as the Python developer don't want to know about eggs, tarballs, debs, rpms, whatevers, I just want to write some software. I'm happy to add a bit of metadata to my setup.py to play ball, but otherwise I really just want one command to release my code and then magically have it appear available to everybody.
That would without a doubt result in an immense mass of broken debs, etc...
On the other end, when I zc.buildout, or paver, or easy_install, or aptitude install, or emerge, or port install, or whatever, it would go out to the Worldwide Python Distribution Network and pull down the proper blobby thing to install based on what I'm trying to do, e.g. an egg if I'm developing, a deb if I'm installing into my system Python, etc.
That sounds very reasonable. That way if you install the foo python library, and it requires libfoo to be installed, it could get the foo.deb, which then would require and install the libfood.deb automatically. That would be very nice. -- Lennart Regebro: Zope and Plone consulting. http://www.colliberty.com/ +33 661 58 14 64