On Thu, Apr 2, 2009 at 3:06 PM, Edward K. Ream <[email protected]> wrote:
>> People may want to manage these files in their version control-system, >> for example. They are not "temporary" files. > > Please remind me. What do these files contain, and why are they important? They are the c.db files, which contain "auxiliary" information used by plugins etc. The plan is to move e.g. frame position and expansion state information (i.e. user specific data) to those files instead of the .leo xml document, where they cause constant unwanted version control conflicts. Seeing that they are a bit unnecessary before being used the first time, I'd be more inclined to postpone the directory creation until after they are accessed the first time. Currently, the only use is storing the list of failed unit tests. >> Uninstall can't remove files that it installed - but do we really care? > > Yes, we care. Uninstall should just work. I'd rather push towards deprecating the .exe installer altogether. It's just not as reliable in any form than just running leo from the directory where you unzipped it. If this is considered highly important, it can be added to preinstall script (this is run for uninstall as well) for bdist_wininst. -- 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 [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 -~----------~----~----~----~------~----~------~--~---
