I'd like to start a new thread here, rather than continue the discussion for bug "911521: Help about and --version should be accurate" so that more people might see it.
Here is my present summary of the situation: The v.bat way is not acceptable: it effectively doubles the number of commits needed, which adds a lot of cruft to the bzr log. But how to fix matters? There are three cases, two of which are almost identical: 1. Running Leo from a bzr repository. This is the easy case. leoVersion.py should get the version from the .bzr/branch/last- revision file. I am going to add this code today. 2. Running Leo from a nightly snapshot. 3. Running Leo from an official release. Cases 2 and 3 are almost identical. The only difference is that for case 3 we could consider running a distribution script to update leoVersion.py. We could also run such a script for nightly snapshots, but that would not be automatic. In short, the essential question is how to update leoVersion.py for nightly snapshots. Terry, I don't recall whether you have ever published the script that builds the snapshots. I think maybe you did, but I have no recollection of it. Would it be possible for this script to update the source code of leoVersion.py? If so, leoVersion.py would get the version from the last-revision file if it exists, and otherwise use the hard coded version inserted by your script. I suppose the essential point here is that updated leoVersion.py would *not* be committed to bzr: it would exist only for the nightly build. This should be safe enough. Any other comments or ideas? Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
