I too would advocate for a "batteries included" model. The philosophy taken by Calibre etc. of including all dependencies in a one click installer that just works.
This is the simplest thing that could possibly work and would enable all of the dicking around be done by the packager, not the user. Compatibility between versions of Qt, Python, OS and Leo should not be a matter for users to sort out. It would eliminate breakage due to upgrades to systems and would provide a much smoother experience for the less technically oriented. Chris On Thursday, December 4, 2014 6:22:19 AM UTC-8, Edward K. Ream wrote: > > > > On Wed, Dec 3, 2014 at 11:04 PM, Davy Cottet <[email protected] > <javascript:>> wrote: > >> >> >> By the way, why not including it into github as a submodule ? >> http://git-scm.com/book/en/v2/Git-Tools-Submodules >> > > Interesting. It may be worth doing. However, it doesn't change import > issues. > > >> >> should I include default installation of all potentially required >> packages (cheditor, pyenchant...) for everything works out of the box ? >> > > Kent has long advocated a "batteries included" philosophy, and I agree. > It would make Leo much easier to install. I would add distutils and sphinx > to the list if possible. > > Edward > > > -- 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.
