I am going to start a new thread because of its importance. I am frustrated and confused regarding all aspects of this topic. The distutils docs seem to be written for somebody else :-) I have at least the following questions:
1. What directory structure must Leo have to make leo a package? 2. My guess is that setup.py should be at the top-most directory, but if that is so, how does it manage to refer to files in inner folders? 3. At present, the createLeoDistribution.py script, which may (or not) form the basis for setup.py, uses the manifest.in file to include/ exclude files. Is this a good idea? 4. At present, running 'python setup.py install' just creates an .egg file in in Python25/Lib/site-packages. What in blazes is going on? More generally, there seems to be too many ways of installing Leo. If I am confused, imagine how Leo's users must feel. I would *really* like to resolve these issues. If Ville or others could help I would be most grateful. Thanks. 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 -~----------~----~----~----~------~----~------~--~---
