Add SVN revision info to egg

[Ryan J Ollos]

Minor configuration management suggestion ...

Would you consider adding a setup.cfg file, like that shown here?

This makes it slightly easier to determine exactly the SVN revision number of an installed egg. This is helpful in case of an installation between version bumps (and as a second check in case a version bump is ever forgotten).

After adding that file to the DateFieldPlugin (and also bumping the version in setup.py) I get TracDateField-1.0.2_r10435-py2.6.egg rather than TracDateField-1.0.1-py2.6.egg.

The SVN revision also shows on the WebAdmin panel:

It is a very minor issue, but I don't know of any downsides. This seems to be a fairly common practice with Trac plugins.

[Chris Nelson]

That seems like a fine change. While it works fine for TH, we use git here so it seems I'd be carrying around a useless file for my local needs. And I wonder what my egg would look like here if I check out from git and build?

[Ryan J Ollos]

Replying to ChrisNelson:

And I wonder what my egg would look like here if I check out from git and build?

I have not tried this, but I think it comes down to what setuptools supports. I'd be really interested to know however, since I've dropped this file into the directory of all the plugins I maintain, and many are using Git and Hg.

[Chris Nelson]

Replying to rjollos:

Replying to ChrisNelson:

And I wonder what my egg would look like here if I check out from git and build?

I have not tried this, but I think it comes down to what setuptools supports. I'd be really interested to know however, since I've dropped this file into the directory of all the plugins I maintain, and many are using Git and Hg.

I guess I'd expect a tag_git_revision that works like tag_svn_revision.

[Chris Nelson]

(In [10477]) Add setup.config. Refs #8986.

Names egg for SVN commit when built from an SVN checkout. Seems to be ignored for builds from git checkout.