On Mon, Jan 9, 2012 at 9:49 AM, Terry Brown <[email protected]> wrote:
>> In short, all that needs to be done is to have leoVersion.py look in >> Leo's core folder for bzr_version.py if last-revision does not exist. >> The core folder is as good a place as any, imo, so there should be no >> need to change your daily build script. >> >> Terry, if you agree I'll change leoVersion.py accordingly. That >> should be the end of the matter. Done at rev 4918. However, I see that bzr_version.py is actually part of Leo's repo. That won't make any difference when running the bzr code, but I suppose this means that your daily snapshot script must take appropriate care not to change it. My guess is that this is what is happening, in fact, but I wanted to raise this issue. Also, I don't have a great way to test the new code that reads bzr_version. Unlike the code that reads the last-revision file, a normal import command suffices to get access. Still, one could imagine that a mistake would cause a crash in the the startup code when running from a snapshot. So we need a new test, and don't have one, other than seeing what happens when using the next snapshot ;-) 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.
