Hi,
I would like to propose again that we deprecate the
sage -upgrade
functionality for "normal end users". It was definitely never
meant to be used by anybody but developers -- in fact I wrote
it mainly for David Kohel (an early Sage developer) who lived
in Australia and consequently had severely capped bandwidth.
My proposal is that
sage -upgrade
displays a message about upgrade in place not being implemented.
Then there is a command
sage -devel_upgrade
(or something) that does the same thing as the current upgrade. However,
it is only to be used by people that really know something about building
Sage and some of the issues that inevitably arise in building package from
source, etc.
Thoughts?
I think the normal upgrade procedure is best done by:
(1) people download a completely new copy of Sage -- this is what
most software,
e.g., vmware, Parallels, etc. that I use on my Mac does, or
(2) for Linux as we get Sage into repositories and building in a
non-monolithic way,
Sage upgrades just go through the normal apt/rpm package management system, or
(3) we do something involving rsync and binaries (???)
-- William
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
