On Mon, 16 Aug 2010 12:55:47 -0500 "Edward K. Ream" <[email protected]> wrote:
> On Sun, Aug 15, 2010 at 8:55 PM, Terry Brown <[email protected]> wrote: > > > > Although it may clash with the philosophy of the NSIS installer, what about > > including Python [and qt] in the .exe installer? > > I see no good way of avoiding using the "official" installers. > > The Python installer is extremely complex: take a look at the links > given above. It would be suicidal to attempt to merge the Python > installer with Leo's installer. I have not looked at the build for qt > installer. It might not be available, but even if it is I have zero > interest in rebuilding it for Leo. Sure, if that was what it takes, it's not feasible. My thought was to set up python, leo, and Qt in a single directory - the directory would then be installed by the "leo" installer, so that you end up with leo and its private copies of python/qt in c:\program files\leo\leo or somesuch. Dumb, inelegant, and the lowest possible barrier to the Leo experience from a user perspective. > > Leo needs to be installed in the system Python for use with other packages, > > but it's very unusual to see an installer for an application which requires > > you to use another installer first. > > That may be, but I see no alternative. The user has two good, > simple, straightforward ways of installing Python and Qt: the > single-click installers and easy_install. > > > If the user knows Python well enough to need Leo to see other packages, > > they can do a `c:\python27\python setup.py install`. If they don't, they > > don't want to have to install Python separately. > > The installer is not equivalent to 'setup.py install.' I do not plan > to distribute setup.py: the comments in this file say that 'setup.up > install' is known not to work. In effect, setup.py is for Ville's > personal use. Moreover, the installer handles registry and other > issues in ways that setup.py doesn't do, and can't do. For example, > the installer creates a proper uninstall line in the control panel. I think uninstall and file associations are less important to someone who wants leo modules installed on the PYTHONPATH. Anyway, my point was that people who might be concerned about Leo/python not being installed in system standard places can probably sort things out for themselves. And people who most need the simplest possible install mechanism won't be concerned about Leo/python not being installed in system standard places. Cheers -Terry -- 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.
