On Mon, Jan 9, 2012 at 9:20 AM, Terry Brown <[email protected]> wrote:
> Actually I think it's just a bug :-) (as opposed to us leap frogging
> each other implementation wise, which is what I thought was happening)
>
> leoVersion.py: /mnt/usr1/usr1/home/tbrown/.leo/.bzr/branch/last-revision does
> not exist
> it's looking in the wrong place, $HOME/.leo instead of directory
> containing launchLeo.py, i.e. one up from leo/
As of rev 4916 the code that computes the location of last-revision is
working well for me.
I just downloaded the latest snapshot, and I see what the problem is.
There is, as expected, no last-revision file. Thus the rev 4916 code
will use the static values.
However, I see that the leo/core directory contains a bzr_version.py
file with the following info::
version_info = {'branch_nick': 'leo-editor-snapshot-20120109',
'build_date': '2012-01-09 02:53:58 -0600',
'clean': None,
'date': '2012-01-08 11:14:52 -0600',
'revision_id': '[email protected]',
'revno': 4917}
The revno looks one too high, but that's a nit.
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.
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.
