> > > but its less error prone imho. > > This is probably true. VirtualBox is massively more widely used. > When we used to distribute a coLinux version of Sage (in 2006), I > remember watching many Windows laptops crash hard due to their > low-level driver. But that was 5 years ago, and things may have > changed by now. > > -- William
With a well-maintained "Sage deployment via VirtualBox image" solution, we would not only address the Windows OS(es)--- but every system where (the minimal version required by the featuers Sage uses of) VirtualBox runs. Both from the user *and* the developer point of view (I easily can load a certain VB image on my OS X and check some error report)! And especially, whenever a new Fedora, RedHat, Ubuntu, Debian, OpenSuse, OS X, Solaris, Windows ... version comes out, where we didn't have the time/resources/whatever yet to make Sage work on it "natively", we always could tell the users at least to use that "Just works!" solution as a fallback. Since there seems to be some need in discussing details, making some decisions, and (most importantly!) to document the latter, why not use the http://wiki.sagemath.org/devel/SEP process (or is there an alternative, better place to do "requirements fixation" for such Sage develop tasks)? Which reminds to check whether I still remember my Sage Wiki login and password ... Cheers, Georg -- 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
