On Thu, May 23, 2013 at 3:30 PM, Matt Wilkie <[email protected]> wrote:
> > Interesting. This looks like a completely different installer than the
> NSIS installer. How did you create the installer?
>
> Specifically: `python setup.py bdist_wininst {options}`
>
I just took a look at setup.py. It's remarkably simple.
Executing the .exe file installs Leo for a particular Python version. This
includes compiling all the .py files to object files, which is useful. In
contrast, the NSIS installer doesn't compile the .py files, which means the
first time the user starts Leo there is a substantial delay. The user
might well be wondering what is happening.
So it looks there has been parallel progress. I would prefer to use
distutils to create the .exe installer.
There is a hook to run a postinstall script to create shortcuts and so on,
> which I haven't tried to figure out yet. Given how much it's taken to
> understand where we're at now I'm not sure I want to either! :)
>
I like the work you have done so far, but I think it's essential that
whatever installer we use will create shortcuts and file associations.
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?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
