Ok, now I've a fully controlled and understood setup.py & MANIFEST.in... hopefully. I had some troubles with my commits so I force a push to go back, I know it's bad and I hope it won't disturb too much. You should now be able to pull an merge from the master branch of my fork : https://github.com/davy39/leo-editor
As I understand it the purpose of splitting a package up into different > pieces to follow local system norms (e.g. Lib to /etc/lib on one and > /opt/lib on another, and not ~/.leo/lib) is in order to accommodated > multiple users. Putting example .leo documents under ~/ is only going to > help that one person -- unless extra intelligence is added to [[insert > something here]] to replicate to all users. Sounds hard to me (but maybe > apt-get or synaptic ... already does stuff like that?) > You are totally right. And I forgot the fact that most of this files are accessible via Leo's menus. So storing these files into installation path is a good strategy, we could maybe just configure Leo to copy those that are potentially modified by users to their personal folder, as I think it already the case for workbook.leo. Otherwise, they are read-only for linux users. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
