Re: What to do about the windows installer?
Edward K. Ream wrote: Problems with the windows installer persist. The 'make' button in dist.leo creates the installer's exe with a pretty gross hack: appending the .zip file to an already-existing .exe file. I don't know whether this hack contributes to the problems users are having. The hack uses the Python 2.5 version of the original .exe file, and the make button ensures that dist.leo was opened using Python 2.5. I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth. I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about this mess? Python went with msi - which is what I would do. Indeed, I was so disgusted by the leo installer for windows that I intended to do this, but somehow have not got around to doing it partly because to make a solution compatible with leo's license, I would have to learn msilib.py - which I need to do anyway, but have not yet done. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: What to do about the windows installer?
On Wed, Jun 24, 2009 at 4:45 PM, James A. Donald jam...@echeque.com wrote: Indeed, I was so disgusted by the leo installer for windows that I intended to do this, but somehow have not got around to doing it partly because to make a solution compatible with leo's license, I would have to learn msilib.py - which I need to do anyway, but have not yet done. Hope you can do something for Leo soon. It would be a big help. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: What to do about the windows installer?
On Jun 17, 9:04 pm, David Szent-Györgyi das...@gmail.com wrote: I gather that the installers for Leo 4.5 and Leo 4.6 are written in Python instead, and that they use the Python-standard tools. See the code in @button make in dist.leo. It's python, but does not use distutils. I gather that one of the goals of the switch to the Python-based installer was to install Leo as a package. I expect that it ought to be possible to use NSIS to drive that intelligently, too. The advantage of the @button make approach is that it uses the .zip file produced by bzr. This eliminates the need for manifests, which always seem to become out of date. Ideally, an automatic NSIS installer would use the bzr .ignore spec to include or exclude files. I have no idea whether that is feasible. The modified installer also checks to make sure that it does not break in various ways. I'll be happy to look at the installer script, but it's not clear that we will ever go back to using nsis. I would prefer to make @button make work :-) Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: What to do about the windows installer?
On Thu, Jun 18, 2009 at 4:14 PM, Edward K. Reamedream...@gmail.com wrote: The modified installer also checks to make sure that it does not break in various ways. I'll be happy to look at the installer script, but it's not clear that we will ever go back to using nsis. I would prefer to make @button make work :-) FWIW, I (briefly) tried setup.py bdist_wininst with bad results. setup.py is most useful right now for direct leo installation from source (setup.py install) or debian packaging. Since nobody is actively supporting any kind of windows installer, it might be better to just instruct windows users to run launchLeo.py from source distribution. py2exe would be cool, but probably very incompatible with our plugin loading system. -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: What to do about the windows installer?
On Thu, Jun 18, 2009 at 2:07 PM, Ville M. Vainio vivai...@gmail.com wrote: FWIW, I (briefly) tried setup.py bdist_wininst with bad results. setup.py is most useful right now for direct leo installation from source (setup.py install) or debian packaging. Since nobody is actively supporting any kind of windows installer, it might be better to just instruct windows users to run launchLeo.py from source distribution. I agree. The windows installer is causing more problems than it's worth. Unless I hear strenuous objections, along with practical solutions to the present installer woes, I will remove the installer stuff from the b2 distribution. This will necessitate revisions to the installation notes and FAQ. Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
What to do about the windows installer?
Problems with the windows installer persist. The 'make' button in dist.leo creates the installer's exe with a pretty gross hack: appending the .zip file to an already-existing .exe file. I don't know whether this hack contributes to the problems users are having. The hack uses the Python 2.5 version of the original .exe file, and the make button ensures that dist.leo was opened using Python 2.5. I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth. I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about this mess? Edward --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: What to do about the windows installer?
On Jun 17, 10:07 am, Edward K. Ream edream...@gmail.com wrote: Problems with the windows installer persist. The 'make' button in dist.leo creates the installer's exe with a pretty gross hack: appending the .zip file to an already-existing .exe file. I don't know whether this hack contributes to the problems users are having. The hack uses the Python 2.5 version of the original .exe file, and the make button ensures that dist.leo was opened using Python 2.5. I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth. I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about this mess? Since I never delivered my modifications to the NSIS-based Windows installer for Leo, you might with justice question my right to comment here. Just let me know whether you want me to share what I got done or what I learned. Details follow. I got the modified installer almost finished before work issues and personal constraints forced me to put it down. The work issues are no longer an issue, and I can manage the personal constraints at this point. I gather that the installers for Leo 4.5 and Leo 4.6 are written in Python instead, and that they use the Python-standard tools. If you wish to apply what I learned to the Python-based installer, I can share what I learned while working on the NSIS-based one. If it would make more sense to go back to the NSIS-based installer, a bit of work should make it possible to incorporate my changes with current Leo and start from there. I tested my modified installer with Leo 4.3 and 4.4 under Windows XP Professional; I did not have access to a Windows Vista box. I do not remember for certain whether I tested it with Python 2.3; I definitely tested it with Python 2.4 and Python 2.5. This modified installer correctly handled installation of a single Leo for all users, using a Python installed for all users. If offered the option of a Leo for the current user only, that worked with a Python installed for that current user only also. Windows makes this set-up relatively easy, and I concluded that this would simplify testing on multiple versions of Python. It also supports testing Leo on multiple installations of a given release of Python, which allows for testing Leo with more than one configuration of Python. The modified installer also checks to make sure that it does not break in various ways. Let me know what you want me to do. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: What to do about the windows installer?
Google Groups hiccuped, and may have devoured my reply. Just in case, I am re-writing it. On Jun 17, 10:07 am, Edward K. Ream edream...@gmail.com wrote: I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth. I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about this mess? Since I never delivered the revised NSIS-based Windows installer that I was working on, you would be entirely within your rights to discount what I write now, but here goes. Let me know what you want me to do. The revised installer is almost finished. It runs on Windows XP Professional; I had no access to Windows Vista for testing. It correctly handles Leo 4.3 and Leo 4.4, and works with Python 2.4 and Python 2.5. It checks for a Python that is installed for the current user, and then it checks for a Python installed for all users. It installs a copy of Leo for the current user only if it finds a copy of Python that is available to that user only. It installs a single copy of Leo for all Windows users when it finds a copy of Python that is available to all users. Installing for the current user only might appear to be of limited importance, but consider how I used it: I created a couple of Windows users for testing the installer, and was able to test with multiple versions of Python, multiple installation scenarios... without breaking the set-up that I used for compiling the installer. I gather that the installers for Leo 4.5 and Leo 4.6 are written in Python. If you think the Python-based installer is worth continuing I will be happy to share what I learned in my work on the NSIS-based installer. If you think it would make more sense to pick up the NSIS installer, a bit of work with my revised version may bring it into the current era. I gather that one of the goals of the switch to the Python-based installer was to install Leo as a package. I expect that it ought to be possible to use NSIS to drive that intelligently, too. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
Re: What to do about the windows installer?
On Jun 17, 10:07 am, Edward K. Ream edream...@gmail.com wrote: I do know that these installer problems are tiresome, and they often create more trouble for users than the installer is worth. I also know that I'm not qualified to fix installer problems. Anyone have any idea what to do about this mess? Since I never delivered my modifications to the NSIS-based Windows installer for Leo, you might with justice question my right to comment here. Just let me know whether you want me to share what I got done or what I learned. Details follow. I got the modified installer almost finished before work issues and personal constraints forced me to put it down. The work issues are no longer an issue, and I can manage the personal constraints at this point. I gather that the installers for Leo 4.5 and Leo 4.6 are written in Python instead, and that they use the Python-standard tools. I gather that one of the goals of the switch to the Python-based installer was to install Leo as a package. I expect that it ought to be possible to use NSIS to drive that intelligently, too. If you wish to apply what I learned to the Python-based installer, I can share what I learned while working on the NSIS-based one. If it would make more sense to go back to the NSIS-based installer, a bit of work should make it possible to incorporate my changes with current Leo and start from there. I tested my modified installer with Leo 4.3 and 4.4 under Windows XP Professional; I did not have access to a Windows Vista box. I do not remember for certain whether I tested it with Python 2.3; I definitely tested it with Python 2.4 and Python 2.5. This modified installer correctly handles installation of a single Leo for all users, using a Python installed for all users. If offers the option of a Leo for the current user only, that worked with a Python installed for that current user only also. This simplifies testing on multiple versions of Python. It also supports testing Leo on multiple installations of a given release of Python, which allows for testing Leo with more than one configuration of Python ... without breaking the set-up that I used for compiling the installer. The modified installer also checks to make sure that it does not break in various ways. Let me know what you want me to do. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups leo-editor group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~--~~~~--~~--~--~---
