On Sunday, 5 February 2012 18:08:46 UTC+8, mmarco wrote: > > On 5 feb, 09:30, Volker Braun <vbraun.n...@gmail.com> wrote: > > I think thats all premature optimization. First we need a bulletproof > way > > of running Sage in the VM. At the end we can still worry about ways to > > shave off another megabyte or two. Most VM questions I got were about > how > > to add more stuff to the VM within its space constraints. Nobody had an > > issue with it requiring a couple of gigabytes of disk space. > > I agree that this is not the most important thing right now. But > incidentally, working on this gave me the idea of separating the guest > OS from the sage install in different files, which, i think, is an > approach to the "automatic generation" that is worth considering. > > But yes, you are right. The most important thing now is to find > someone that would write the windows gui to take care of the VM, and > then a lot of testers to detect the possible ways it could fail.
there is no need for "custom" gui: plenty of tools around allows one to build installers doing nontrivial things. One such thing 15 years ago was InstallShield, they seem to be still in business. A free one is Innosetup: http://www.jrsoftware.org/isinfo.php Cygwin has its own GUI installer written from scratch. M$ has its own Windows Installer (which was, and probably still is, a nightmare, as usual with M$ products). Dima Do not forget that you ideally also want updates to be done more or less automatically. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
