At 07:40 PM 5/29/2005 -0500, Ian Bicking wrote: >Well, one way is to have _download_svn() put that metadata into the >downloaded files -- some special file -- to later be read by >setuptools. That would fit into a downloadable snapshot as well. And >obviously _download_svn() can't work without svn installed. It should >also be reasonably easy to translate to other version control systems, >insofar as they have useful revision numbers. Though I don't think many >of the distributed systems do :( Unless you are okay with *really* long >versions that essentially embed a UUID -- but I don't encounter any of >those repositories, so it's not a problem for me yet.
I think this is all YAGNI; I'd like to encourage people to distribute ready-to-use eggs for their users. If you're involved with a project that has active development and you need to build-to-rev, I think it suffices to allow arguments to be passed through to the setup script (like --tag-date and --tag-svn-revision). Really, though, I don't see why you couldn't just set up your svn repository to request building a new egg (and/or source distribution, appropriately tagged) whenever a commit takes place under the project tree. _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
