Ed Leafe wrote: > but of course this reliance on using "HEAD" as a revision number > completely breaks web update, since now there is no way to tell what > they have, so there's no way to tell whether they are behind or not. > It seems that unless you have the full Subversion program installed > (it fails with TortoiseSVN, which doesn't install command-line > tools), you won't be able to use web update, which seems completely > wrong.
Well, this was a problem before, too. The revision in the __version__.py stuck at the released revision unless you used Subversion. Ditto if you used Tortoise without the svn commandline. > Isn't there some way that you can automate the repository so that > any commit also changes the __version__.py file? It is possible, but I believe it would require Subversion wizardry that is beyond my ability or available time to muddle through. I'd have to modify the Subversion transaction in the pre-commit hook to stuff that change in. Or, in the post-commit hook I could do another complete subversion transaction, resulting in each commit incrementing the revision by 2 instead of 1. This would be fairly straightforward, but I'd have to keep the incrementing from being recursive, and it feels fairly hokey to have each commit increment by 2. But, the last time I looked at this was a couple years ago, and Subversion has changed since then, and more people have probably wrestled with and found solutions to the same or similar problems, and I've gained knowledge, too. So I'll dig into this again, as I agree it isn't correct (it never has been). -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
