On Mon, Feb 6, 2012 at 17:20, Emil Widmann <emil.widm...@gmail.com> wrote: > I think the unionfs is a well tested technology now, but a clean > solution would be that in case of such an replacement/upgrade of the > sage squashfs the whole sage directory tree in the save directory is > deleted too - then the user starts with a "fresh" install.
That's what I think too, but it disagrees with the current behavior of `sage -upgrade`, which tries to merge any committed changes into the new version you're upgrading to. That doesn't make sense IMO but there you are. > Sounds great! > This could be just a small application in the beginning with the sage > logo and a start button , but can be expanded later. > I am not sure if it is necessary to write this in python - that is > another dependency. > Why not use VBscript or precompile it? Distribution of binaries on > windows should be no problem. Python programs can be made into Windows binaries with py2exe_, a distutils extension. GUIs can be made relatively easily with PySide_, or so I've heard - haven't gotten around to trying it myself yet. .. _py2exe: http://py2exe.org/ .. _PySide: http://pyside.org/ I wonder why you suggest using VBscript. It's not exactly a majority / serious language among Windows developers as I recall and certainly nobody on Mac or Linux uses it. I think we should stick to Python if possible for widest familiarity among our developers. Maybe you just meant that it is a built-in scripting language in Windows, which is true, but as you said, there's no problem in shipping binaries for Windows. -Keshav ---- Join us in #sagemath on irc.freenode.net ! -- 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