Rev 2401 of the trunk now contains an installer that will install in python/Lib/site-customize rather than c:\Program Files.
It is becoming apparent that David's suggestion to separate boilerplate from the files lists is a good one. This will make working on the boilerplate much easier. My present plan is to create an @auto nsi.boilerplate.txt node, containing just about everything not in the files lists. The drawback is that install script isn't so directly application independent. That is, the boilerplate would have to be rewritten/ revised for different applications. But the present scheme (substituting constants in python triple-quoted strings when the substitute argument to put is True) is too confusing. In retrospect, trying to making the script application independent seems to have added a lot of work for very little gain. I definitely would like to rewrite the script this morning, so that I can create a 47-maint branch. Time is running out if we want to release Leo 4.7 b1 before I leave for vacation. 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 -~----------~----~----~----~------~----~------~--~---
