I think its still up for discussion what the best strategy of running Sage 
in VirtualBox is. I feel that textmode Sage server using the native browser 
as interface is the most natural way since there is no confusion about which 
web browser to use. The disadvantage is that we can't automatically open a 
browser from the sage process with a magic url, so the user has to log in 
manually. You don't need any GUI to install the sage combinat patches. 

For developing Sage you should probably install Linux first. Still, if you 
have to use a VM for some reason then I think its better to export the sage 
directory via Samba than have a GUI editor run inside the VM. If you are 
happy with vi/emacs then you probably run Linux already...

The VM is larger than before because it is not particularly tuned for the 
minimal number of packages. There is a certain trade-off between minimal 
size and making it easy to create the base linux install, and I don't see 
much point in spending time to save a little bit of hdd space. Adding 
latex/libpng/libjpg/cairo will make it even bigger, but again I think 
usability is more important than space savings.

-- 
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

Reply via email to