Edward K. Ream wrote: In essence, this file would be a VM (Virtual Machine) containing: >
VMs are heavy on the performance, need additional software and integrate bad into the system. Also, VMs need an underlying OS, which would mean some Linux-Distribution which run parallel to the existing OS. If the user has Windows, it would only alienate them. What speaks against a traditional executable package? py2exe and PyInstaller are existing and were working well the last time I used them. Using docker or a VM for a simple Desktop-App is very overstretched for "normal" users. It might work as an solution for specific scenarios. On the Mac, Leo could be delivered as a Homebrew formula (assuming we ever > figure out how ;-), but again, Homebrew itself must be installed first. > There is also a fork to linux, called linuxbrew. On debian and ubuntu there is no native package for leo, so this might be a general solution for this plattform too. I just tried out the leo.rb from your mergerequest (after fixing it and updating to 5.1), but so far it fails with some (known) openssl-failures. So maybe some in days it will work. I'm also curious why you don't deliver the files directly from github, instead from sourceforge? The content seems to be the same? -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
