On Jan 7, 1:34 am, Dan Drake <dr...@kaist.edu> wrote:
> On Wed, 07 Jan 2009 at 12:31AM -0800, mabshoff wrote:
Hi Dan,
> > Well, it took the better part of the night, but I finally got Sage
> > 1.0.0 to build and start on sage.math. William dared me in IRC to do
> > this last night, but I showed him [being obviously aware of reverse
> > psychology here :)]
>
> > mabsh...@sage:/disk/scratch/mabshoff-sage-releases/sage-1.0.0$ ./sage
> > --------------------------------------------------------
> > | SAGE Version 1.0.0, Build Date: 2006-02-04-0049 |
> > | Distributed under the GNU General Public License V2 |
> > | For help type <object>?, <object>??, %magic, or help |
> > --------------------------------------------------------
>
> If you got it to build last night, why does it say February 4, 2006? Is
> that the release date?
Yes, I guess back in the day build date meant release date. And
apparently it was release around 0:49 am, just in case one wants to do
more than one release per day :)
> > I have also thought about how one could distribute these and would
> > suggest the following: Set up a VMWare image with LTS 8.04 and the
> > older compilers I build in order to get the old stuff to compile. Then
> > -bdist all the installs and put them up on some webspace. The image
> > would then have a menu that downloads a list of given version and the
> > user can then select sage-x.z.y and install it in parallel locally
> > with other installs. At the same time it should be possible to deleted
> > installs and so on. That way we can have a on-demand repo to install
> > any reasonable version of Sage for this particular VMWare image. Given
> > that LTS 8.04 has support until 2013 it seems that plenty of version
> > should be available by then. If someone wants to do this or make it a
> > student project for a minion I am more than happy to write up a SEP
> > for someone to use as a basis for an implementation.
>
> Technically, it's only the server version that is supported to 2013; the
> desktop version is supported for three years, to 2011. And it's probably
> only the "main" repo that is guaranteed to get updates; restricted,
> universe and multiverse will not, I think, get security updates.
Well, we are running LTS server because we wanted the long support
phase. And as long as we get security updates that is fine with me. If
things get too outdated, i.e. the modern gcc's won't compile any more
just like glibc was too old for gcc 4.3 on sage.math we need to decide
what to do.
> (I haven't been able to find a definitive answer to what "supported"
> means; is it everything in main and restricted, or what?)
>
> At any rate, the next LTS is 2010 so we'll have a year to update the
> VMWare image. I'm sure it won't be problem.
Well, I am not sure this upgrade will guarantee that binaries from
this LTS will run unchanged (I assume they *wont*). It might even be a
challenge to get gcc 4.0.4 or 4.1.2 to compile and once that
possibility is gone we can no longer compile anything before 2.8.14
without starting to fix build bugs which is a possibility, but a pain.
We can obviously preserve the old VMWare image we are using now and
have it provide every Sage release since 1.0 since in 3 years or so a
150 GB or so uncompressed VMWare image won't be "large" any more
(assuming 125 or so images total since 1.0 since then). The hope is
that in 30 years we can still run the oroginal Sage 1.0 binary created
today if we want to even if at that point it might be an emulation
inside an emulation .... :)
> Overall, this is a great idea!
I agree obviously :)
> Dan
Cheers,
Michael
> --
> --- Dan Drake <dr...@kaist.edu>
> ----- KAIST Department of Mathematical Sciences
> ------- http://mathsci.kaist.ac.kr/~drake
>
> signature.asc
> < 1KViewDownload
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
