On Thu, 14 Aug 2014 09:26:30 -0700 (PDT) Chris George <[email protected]> wrote:
> "It's not ok to require that people use `git` to get it, > that's unreasonable." > > Why? > > The primary target user for Leo is a programmer, is it not? No, although I can understand why someone might think that was the case :-) Also, there are programmers (the docutils dev. team for example) who are not interested in using git, and would probably regard needing to use it to download and try a piece of software as a reason not to try the software. > Perhaps > once the development solidifies enough and begins targeting > non-programmers (average user), then it might need a little dumbing > down of the distribution method. > > I may be a bit on the edge as a user, I use a rolling distribution > for my operating system so I am familiar with the model, but Leo is > currently fluid, and as a user that is one of its strengths to me. > Installing git and writing a script to pull down the latest Leo and > start it was simple, and I can't see it being any more difficult on > other platforms. I guess I see the use of git as a feature. :-) For a programmer. I think expecting people to unzip a zip is not unreasonable, although it will screen out some people, but they were probably not going to find Leo to their liking. Hence the problem with the .zip reporting misleading version info. Cheers -Terry > Chris > > On Thursday, August 14, 2014 8:59:02 AM UTC-7, Terry wrote: > > > > On Thu, 14 Aug 2014 10:40:23 -0500 > > "Edward K. Ream" <[email protected] <javascript:>> wrote: > > > > > On Thu, Aug 14, 2014 at 9:02 AM, Dufriz <[email protected] > > > <javascript:>> > > wrote: > > > > I am on Windows 8.1, running Python 3.3.5 with > > > > PyQt4-4.10.4-gpl-Py3.3-Qt4.8.5-x64. > > > > I am using Leo 4.11 final, build 6240. > > > > > > Thanks for this. This looks like ancient history, though I might > > > be mistaken. Recent builds (from git) look like: > > > > > > Leo 4.11 final, build 6e21a6dc12f0 (branch: master), 2014-08-13 > > > 08:30:03 > > > > That's a good point of course, my comments about needing "c, " > > added in that call apply to the current trunk, not sure about that > > version. > > > > Actually.... Houston, we have a problem. > > > > Leo uses the model "use the trunk, it's stable" - ok > > > > It's not ok to require that people use `git` to get it, that's > > unreasonable. > > > > But no problem, they can use the snapshot, > > https://github.com/leo-editor/leo-editor/archive/master.zip > > > > But... that identifies itself in the log window as > > > > Leo 4.11 final, build 6240, 2013-11-06 > > Python 2.7.6, PyQt version 4.8.6 > > > > which is completely misleading. It does that because it falls back > > on version.py or similar, I assume, when the .git directory's not > > present. > > > > So, we need a git commit hook to update version.py on every commit. > > > > Or, not use git-hub for snapshots, but it seems git-hub is so close > > to doing exactly what we need it's worth getting version reporting > > in git-hub snapshots to work. > > > > (Summary - quite possibly Dufriz is using the latest code, can't > > tell from the log pane content) > > > > Cheers -Terry > > > > > Could you pull down the latest git version? Alternatively, you > > > could get a recent daily snapshot? That way we can all be > > > discussing recent code. If you use git you can instantly get any > > > improvements. > > > > > > Edward > > > > > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
