Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#11081 closed enhancement (fixed)

Update the "Install from Source Code" section of the Sage Installation Guide

Reported by: drkirkby Owned by: mvngu
Priority: blocker Milestone: sage-4.7
Component: documentation Keywords:
Cc: jhpalmieri, kcrisman Merged in: sage-4.7.alpha4
Authors: David Kirkby Reviewers: Karl-Dieter Crisman, Florent Hivert, John Palmieri, Dmitrii Pasechnik, Jeroen Demeyer
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by jdemeyer)

The Sage installation guide has a section on installing Sage from source

http://www.sagemath.org/doc/installation/source.html

but it is inaccurate, incomplete and dangerous in certain places. Specific problems are below. These are roughly listed in the order they appear in the manual.

  • It fails to point out one of the advantages of building from source is that certain parts of Sage get optimised for ones own computer.
  • It has a list of supported systems, which is outdated, so I replaced that with a link to http://wiki.sagemath.org/SupportedPlatforms. Current it has outdated comments like:
    • We hope to support OS X 10.5 in our next release and
    • We do plan to fully support Solaris - it’s a very important platform.
  • The information about perl is inaccurate. This is also needed for R, and it must be at least perl 5.8.0. I added the list of versions of software where appropriate.
  • It suggests use of the which command, but a more portable version is to use command -v, as which is not a required component of a UNIX operating system - it is not defined by POSIX and was the source of one issue on Solaris.
  • It says if which m4 returns nothing or an error than m4 is not installed. But it could well be installed, but not in the PATH.
  • There's a comment about the m4 command. I added a note this was installed in /usr/ccs/bin on Solaris, as this is far from obvious. There are a few other Solaris notes I made.
  • It says you need to have ssh-keygen installed to run the server in secure mode, which is true. It then says To run it in insecure mode, run the command notebook(secure=False) instead of notebook() but this is incorrect, as the default is to run in insecure mode.
  • It recommends on installs the readline package, yet this is part of Sage.
  • It says Sage is currently being developed using GCC version 4.3.x, whereas in fact Sage tends to be developed with pretty recent versions of the compilers.
  • There's a reference to a system wide gFortran, whereas the command has no capital F.
  • It says starting Sage for the first time can take a few seconds. I changed that to a few minutes, as running Sage for the nth time, where n>1 can take more than a minute on some systems.
  • I changed the version numbers and dates of a few commands. The example of running Sage shows SAGE Version 3.1, Release Date: 2008-08-16 I replaced that with a more recent version.
  • An example shows GAP4, Version: 4.4.6 of 02-Sep-2005 so I changed that to the current version in Sage (GAP4, Version: 4.4.12 of 17-Dec-2008). That also happens to be the latest version, so I don't know if GAP development has ceased, or just taken a long break.
  • As with GAP and Sage, I changed the example to show a more recent version of Singular.
  • I changed the fact testing was Optional to Optional, but highly recommended.
  • Probably not necessary, but I changed the times to build Sage from 30 minutes to an hour or longer to span a wider range of times.
  • Removed the information about deleting files in $SAGE_ROOT/spkg/build to save 500 MB of disk space, as that's no longer true - they get deleted after each package is built. One or two packages do remain there (like prereq), but deleting them won't save much disk space.
  • Change nonempty to non-empty in several places.
  • Since there were some comments about building Sage from source as root, mainly due to Luis Finotti, I felt obliged to add my own comment that I think building Sage as root is dangerous, and provided a link to a trac bug (#9551) where Sage would have overwritten a system file had I been stupid enough to build as root.
  • As much as I think it's silly building Sage as root in /usr/local, I updated the version of the example from 2.5.2 to 4.6.2.

I've put quite a bit of work into this, and I think generally it is an improvement. I'll be receptive to constructive comments. But PLEASE PLEASE PLEASE can we avoid what happens on tickets some times, when tons of people argue about the smallest of details and tickets drag on for months. If the comments drag on and on, I might ask that someone review the patch as it is, and create another ticket to fix further changes. People can always create other tickets for other changes.

Notes for reviewers and the release manager

  1. Apply only 11081_all.patch

Attachments (6)

11081-install-from-source.patch (17.3 KB) - added by drkirkby 10 years ago.
Mercurial patch for changes to documentation. I hope this is an improvement, and hope requested changes don't drag on for a long time.
11081-install-from-source-Additional-information.patch (23.2 KB) - added by drkirkby 10 years ago.
Additioanl information, addressing reviewer comments. To be applied after 11081-install-from-source.patch
11081-minor-changes.patch (3.4 KB) - added by drkirkby 10 years ago.
To be applied after the two earlier patches
11081-dont-use_GCC_4_3_2.patch (3.4 KB) - added by drkirkby 10 years ago.
Patch to advise uses not to use gcc 4.3.2, which Bill Hart said on sage-devel today that it mis-compiles MPIR on x64.
11081-use-recent-gcc.patch (2.7 KB) - added by drkirkby 10 years ago.
Suggest use of recent gcc. Drop mention of gcc 4.3.2 being bad.
11081_all.patch (31.6 KB) - added by jdemeyer 10 years ago.
All patches folded

Download all attachments as: .zip

Change History (39)

Changed 10 years ago by drkirkby

Mercurial patch for changes to documentation. I hope this is an improvement, and hope requested changes don't drag on for a long time.

comment:1 Changed 10 years ago by jhpalmieri

  • Cc jhpalmieri added

comment:2 Changed 10 years ago by kcrisman

  • Cc kcrisman added

comment:3 follow-up: Changed 10 years ago by kcrisman

  • Reviewers set to Karl-Dieter Crisman
  • Status changed from new to needs_work

A few comments for improvement:

  • I think it would be nice to have at least the main "fully supported" versions here. No need to go clicking through if you are on a normal system, then, and also it will be clear that e.g. Windows 7 is not on that list just by looking at it. Something like "supported on many Linux distributions, Mac OS X, and 32-bit Solaris; see ... for details and status of other systems." I'm not wedded to that phrasing, but it's reasonable to have at least minimal info.
  • A minor note should be added that gfortran is not provided by Xcode on OS X, but that Sage provides a suitable Fortran compiler for OS X.
  • Even for my ancient < 1 GHz Emac (probably from around 2003), it takes less than a minute for Sage to start up the first time (though it's close!). I think it is more reasonable to say "starting the first time may take more than a few seconds; a few platforms will take longer for reason X" where it is clear that reason X is something about the platform, not Sage.
  • "Note from David Kirkby. " - is that going to look ok in the docs? Maybe instead using the ".. note:" syntax...

All the updates etc. and changes for more accurate documentation look fine, though I'm sure more knowledgeable folks will have some minor changes there, since it's a rule that any patch longer than 1 character has a bug :-)

Nice work cleaning this up, Dave. We are very fortunate that Sage has enough people who care about this kind of thing that we do eventually clean them up!

comment:4 in reply to: ↑ 3 ; follow-up: Changed 10 years ago by drkirkby

Replying to kcrisman:

A few comments for improvement:

  • I think it would be nice to have at least the main "fully supported" versions here. No need to go clicking through if you are on a normal system, then, and also it will be clear that e.g. Windows 7 is not on that list just by looking at it. Something like "supported on many Linux distributions, Mac OS X, and 32-bit Solaris; see ... for details and status of other systems." I'm not wedded to that phrasing, but it's reasonable to have at least minimal info.

OK, point taken. I'll keep that to the bare minimum though. I don't think its true to say Sage is "supported on many Linux distributions" when we only test on a few. The issue we had before was a huge range of "supported" Linux distributions, which nobody had tested on for ages, if at all.

  • A minor note should be added that gfortran is not provided by Xcode on OS X, but that Sage provides a suitable Fortran compiler for OS X.

I can add that, though the current documentation does say in this very file:

On Mac OS X, you are not required to have a Fortran compiler on your system. The Sage source distribution is shipped with a Fortran compiler for Mac OS X. This Fortran compiler is used, unless you specify another Fortran compiler via the variable SAGE_FORTRAN.

  • Even for my ancient < 1 GHz Emac (probably from around 2003), it takes less than a minute for Sage to start up the first time (though it's close!). I think it is more reasonable to say "starting the first time may take more than a few seconds; a few platforms will take longer for reason X" where it is clear that reason X is something about the platform, not Sage.

I hear plenty of complaints on sage-devel of Sage taking a very long time to start.

  • "Note from David Kirkby. " - is that going to look ok in the docs? Maybe instead using the ".. note:" syntax...

In my opinion it looked ok, but perhaps I'm biased. I don't know how to use the note syntax. I wanted to make this quite prominent, as I think its a pretty important point. We are documenting how to do something that any decent system administer knows one should never do.

All the updates etc. and changes for more accurate documentation look fine, though I'm sure more knowledgeable folks will have some minor changes there, since it's a rule that any patch longer than 1 character has a bug :-)

Yes, I just want to avoid it becoming like tickets have become. I feel quite sorry for John, as I feel that reviewers have requested changes far outside the scope of some of John's tickets.

Nice work cleaning this up, Dave. We are very fortunate that Sage has enough people who care about this kind of thing that we do eventually clean them up!

I think documentation will always tend to be out of date. We can however limit that by not being too specific. The original version saying developers use gcc 4.3.x was just asking for trouble.

Dave

comment:5 in reply to: ↑ 4 ; follow-up: Changed 10 years ago by kcrisman

  • A minor note should be added that gfortran is not provided by Xcode on OS X, but that Sage provides a suitable Fortran compiler for OS X.

I can add that, though the current documentation does say in this very file:

On Mac OS X, you are not required to have a Fortran compiler on your system. The Sage source distribution is shipped with a Fortran compiler for Mac OS X. This Fortran compiler is used, unless you specify another Fortran compiler via the variable SAGE_FORTRAN.

Is it anywhere near where your thing is? My concern was people on OS X thinking they needed to get/had gfortran.

  • Even for my ancient < 1 GHz Emac (probably from around 2003), it takes less than a minute for Sage to start up the first time (though it's close!). I think it is more reasonable to say "starting the first time may take more than a few seconds; a few platforms will take longer for reason X" where it is clear that reason X is something about the platform, not Sage.

I hear plenty of complaints on sage-devel of Sage taking a very long time to start.

They mean >5 sec, or >2 sec. on a fresh cache. Not minutes. Anyway, there are very few systems, I think, where 'minutes' is the right word, and we don't want to scare people.

  • "Note from David Kirkby. " - is that going to look ok in the docs? Maybe instead using the ".. note:" syntax...

In my opinion it looked ok, but perhaps I'm biased. I don't know how to use the note syntax. I wanted to make this quite prominent, as I think its a pretty important point. We are documenting how to do something that any decent system administer knows one should never do.

I haven't looked at it in the doc yet, so we'll see when we get there.

comment:6 in reply to: ↑ 5 Changed 10 years ago by drkirkby

Replying to kcrisman:

  • A minor note should be added that gfortran is not provided by Xcode on OS X, but that Sage provides a suitable Fortran compiler for OS X.

I can add that, though the current documentation does say in this very file:

On Mac OS X, you are not required to have a Fortran compiler on your system. The Sage source distribution is shipped with a Fortran compiler for Mac OS X. This Fortran compiler is used, unless you specify another Fortran compiler via the variable SAGE_FORTRAN.

Is it anywhere near where your thing is? My concern was people on OS X thinking they needed to get/had gfortran.

They mean >5 sec, or >2 sec. on a fresh cache. Not minutes. Anyway, there are very few systems, I think, where 'minutes' is the right word, and we don't want to scare people.

Fair enough. As a matter of interest, William wrote here

http://www.mail-archive.com/sage-devel@googlegroups.com/msg46733.html

"Indeed, if it takes 5-10 minutes for Sage to start (and yes it does on some slow filesystems), then this wouldn't help at all"

but I guess that is the exception rather than the rule. It takes 30 s on my 2.0 GHz laptop. It appears to be I/O limited. I'll mention that.

  • "Note from David Kirkby. " - is that going to look ok in the docs? Maybe instead using the ".. note:" syntax...

In my opinion it looked ok, but perhaps I'm biased. I don't know how to use the note syntax. I wanted to make this quite prominent, as I think its a pretty important point. We are documenting how to do something that any decent system administrator knows one should never do.

I haven't looked at it in the doc yet, so we'll see when we get there.

I'll make some revisions and post an update. Then perhaps you can generate the documentation and look at in a browser.

Dave

comment:7 follow-ups: Changed 10 years ago by jdemeyer

Line 131 in the new file: it is false that PARI needs perl (it might have been true some time in the past, I don't know). Only the PARI/GP documentation (not installed or used by default) needs perl.

Line 752 in the new file: the comment about PARI's galois data files is also completely outdated and should be removed.

By the way, "starting the first time can take a few minutes" is totally true when you have a slow disk on a busy system (e.g. sage.math.washington.edu)

comment:8 in reply to: ↑ 7 ; follow-up: Changed 10 years ago by drkirkby

Replying to jdemeyer:

Line 131 in the new file: it is false that PARI needs perl (it might have been true some time in the past, I don't know). Only the PARI/GP documentation (not installed or used by default) needs perl.

Line 752 in the new file: the comment about PARI's galois data files is also completely outdated and should be removed.

I'll make those changes.

By the way, "starting the first time can take a few minutes" is totally true when you have a slow disk on a busy system (e.g. sage.math.washington.edu)

How about saying:

"Sage should take well under a minute to start for the first time, but it can take a few minutes on a slow or busy file system?"

I did also think of putting something to the effect of

If possible install Sage on a local disk or fast system, as Sage loads a large number of files, which can mean Sage is slow to start on some file systems.

The trouble with these changes is that they are subjective. Most of the other points are just correcting indisputable facts.

I think one useful addition to the bottom of a page might be

"Last updated on x/y/z"

so hopefully we can find pages that are well out of date.

It's hard to believe that a page as important as describing how to build Sage from source has so many inaccuracies in it. I suspect this has not been properly updated for a few years.

comment:9 in reply to: ↑ 7 Changed 10 years ago by drkirkby

Replying to jdemeyer:

Line 131 in the new file: it is false that PARI needs perl (it might have been true some time in the past, I don't know). Only the PARI/GP documentation (not installed or used by default) needs perl.

Thinking about this particular point, I don't see the need for documenting what component(s) of Sage uses Perl. I added R, as there were already packages mentioned, but really all the user needs to know is that they need a version of Perl that is >= 5.8.0. Whether it's use by R, NTL, Pari or foobar is not really important.

Dave

comment:10 in reply to: ↑ description ; follow-up: Changed 10 years ago by dimpase

Replying to drkirkby

regarding the version of XCode for MacOSX, I think it's safer to say that we expect a recent version of XCode for the relevant MacOSX platform version, as we don't test on outdated XCode versions.

comment:11 in reply to: ↑ 10 Changed 10 years ago by drkirkby

Replying to dimpase:

Replying to drkirkby

regarding the version of XCode for MacOSX, I think it's safer to say that we expect a recent version of XCode for the relevant MacOSX platform version, as we don't test on outdated XCode versions.

Thank you. I'll say "recent" and suggest looking at http://wiki.sagemath.org/SupportedPlatforms for the supported versions of Xcode. That way, we can more easily make changes on the Wiki. Since this page does not tend to get updated very often, I want to avoid putting anything that is likely to be out of date soon.

I'll apply another later, with changes people have suggested.

Dave

comment:12 Changed 10 years ago by drkirkby

  • Status changed from needs_work to needs_review

I'm attaching a patch which makes the following changes - again roughly listed in the order they are mentioned in the document.

  • Provide some hyperlinks to external sites such as Wikipedia where I felt it might be appropriate.
  • Provided a list of the supported platforms (Linux, OS X, Solaris and OpenSolaris), but did not go into many details about these.
  • Added a note that gfortran does not come with Xcode, but that Sage includes an executable for a Fortran compiler on OS X.
  • Stated Sage is not supported on Windows except via a virtual machine and added a link to Wikipedia to explain what a virtual machine is.
  • Increased the disk space needed from 2 to 2.5 GB. I think 2 GB is just about enough now, but I doubt it will be for long. (In fact, a 64-bit on Solaris is taking over 3 GB)
  • Removed the comment that Xcode is a free download and stated there may be a charge. (I see it costs $4.99, although I did not state the amount).
  • Added minimum versions of GNU make and GNU tar. (I don't actually know what are the minimum versions for this, but I know the versions shipped with the first release of Solaris 10 in 2005 will build Sage, so I put them as minimum versions)
  • Removed comments about what uses Perl. (It now just states Perl is needed, with no explanation of why, although the minimum version is stated).
  • Changed the wording of the startup time of Sage to read starting the first time should take well under a minute, but can take several minutes if the file system is slow or busy. Since Sage opens a lot of files, it is preferable to install Sage on a fast file system if this is possible. (I believe those are all indisputable facts)
  • Added that one could install things like binutils if one has the right privileges, and if not to ask the system administrator.
  • Removed comments there must be a system-wide install of gfortran, and changed it to be a system wide or a personal installation.
  • Removed comment about Sage not building with gcc 4.3, as I can find nothing to suggest this is the case now.
  • Removed the suggestion to compile Sage as root, and suggest this is not done. (Since the bug with PARI's galois data files has been resolved, there seems no good reason to compile Sage as root.)
  • State on Mac OS 10.4, 10.5, Solaris and OpenSolaris one should set SAGE64 to yes before running make. (Also stated 64-bit Solaris builds are unstable)
  • Suggested that one runs
    grep "An error occurred" spkg/logs/*
    
    if a build error occurs, and to put the output of that on sage-support. (Previously the documentation said to attach install.log, but its totally impractical to attach a file the size of install.log to an email).
  • Removed the Note from David Kirkby advising one not to build as root.
  • Added at the bottom of the page This page was last updated in April 2011

I believe there are still improvements that could be made, but believe the changes made are a good compromise between improving the accuracy and spending too much time over minor details.

Dave

Changed 10 years ago by drkirkby

Additioanl information, addressing reviewer comments. To be applied after 11081-install-from-source.patch

comment:13 Changed 10 years ago by drkirkby

  • Description modified (diff)

comment:14 in reply to: ↑ 8 ; follow-up: Changed 10 years ago by jdemeyer

  • Priority changed from major to blocker

Replying to drkirkby:

I think one useful addition to the bottom of a page might be

"Last updated on x/y/z"

Personally, I dislike non-automatic "last updated" lines like this one. People will forget to update the "last updated" line when making changes to the file. Also, I don't see much usefulness in such a line.

It would be really good to have this in sage-4.7.

comment:15 in reply to: ↑ 14 ; follow-up: Changed 10 years ago by drkirkby

Replying to jdemeyer:

Replying to drkirkby:

I think one useful addition to the bottom of a page might be

"Last updated on x/y/z"

Personally, I dislike non-automatic "last updated" lines like this one.

Do you know a relieable automated way?

People will forget to update the "last updated" line when making changes to the file.

Well, hopefully either the author or reviewer would notice.

The worst that can happen if someone forgets to update the line (and the reviewer does not notice), is that users will think the information is more outdated than it really is.

Also, I don't see much usefulness in such a line.

Users can determine if the information is current, which is quite important with information like this. It can tend to go out of date. If users see the information was written a year or more ago, they might realise its probably inaccurate.

It would be really good to have this in sage-4.7.

I'm glad you think it would be useful. I'm surprised you updated it to blocker (though I'm not complaining, but I'd like to see 'prerequisite checks #11070 / #9978 in more!) But more seriously, we really need to stop such an important part of the documentation getting so out of date. Clearly many people will build Sage from source, yet so much of the information was inaccurate.

If you feel strongly about it, I'll remove the "last update" bit.

Dave

comment:16 Changed 10 years ago by hivert

Just a quick remark: I was passing by and I noticed that the it following paragraph there is a parenthesis opened but not closed

  
 	73	(You must have the GNU version of ``make`` installed and it must be the first 
 	74	``make`` in your PATH. On Solaris, a version of GNU ``make`` may be found  
 	75	at ``/usr/sfw/bin/gmake`` but you will need to copy it somewhere else 
 	76	and rename it to ``make``. The same is true for GNU tar - there is a version 
 	77	called ``gtar`` in ``/usr/sfw/bin`` but it will need to be copied somwhere 
 	78	else and renamed to ``tar``.  

comment:17 in reply to: ↑ 15 Changed 10 years ago by jdemeyer

Replying to drkirkby:

If you feel strongly about it, I'll remove the "last update" bit.

I do not feel strongly about it.

comment:18 Changed 10 years ago by jhpalmieri

Would it be better to change the paragraph on supported systems from

Sage is supported on ...

to

As of April 2011, Sage is supported on ...

Then anyone who changes the list of supported platforms are more likely to see the date than if the date is at the bottom of the document. (I know the other information in the document is also time-sensitive, but not quite as much as the list of supported platforms.)

Alternatively, we could add something like this to the very top of the file:

.. comment:
   ****************************
   If you alter this document, please change the last line ("This page
   was last updated on ...")
   ****************************

comment:19 Changed 10 years ago by drkirkby

  • Reviewers changed from Karl-Dieter Crisman to Karl-Dieter Crisman, Florent Hivert, John Palmieri, Dmitrii Pasechnik, Jeroen Demeyer
  • Status changed from needs_review to needs_work

I'll attach another patch in a couple of minutes, using the comment as suggested by John. I also noticed another typo, and a couple of very minor changes.

Changed 10 years ago by drkirkby

To be applied after the two earlier patches

comment:20 Changed 10 years ago by drkirkby

  • Description modified (diff)
  • Status changed from needs_work to needs_review

I'm marking this for "needs review" now.

Changed 10 years ago by drkirkby

Patch to advise uses not to use gcc 4.3.2, which Bill Hart said on sage-devel today that it mis-compiles MPIR on x64.

comment:21 Changed 10 years ago by drkirkby

  • Description modified (diff)

I changed the supported version of gcc to say not to use gcc 4.3.2, as apparently this mis-compiles MPIR according to Bill Hart who is an MPIR developer.

comment:22 follow-up: Changed 10 years ago by jdemeyer

David, there are so many bad versions of gcc miscompiling various packages that it's pointless to start making a list. Better state something along the lines of "(Version 4.0.1 or later, but preferably a recent version)"

comment:23 in reply to: ↑ 22 Changed 10 years ago by drkirkby

  • Status changed from needs_review to needs_info

Replying to jdemeyer:

David, there are so many bad versions of gcc miscompiling various packages that it's pointless to start making a list. Better state something along the lines of "(Version 4.0.1 or later, but preferably a recent version)"

OK, will do. But is it worth documenting that some versions don't work on particular platforms, without going into details about which versions and on which platforms? (Such detail could be added to the Wiki at http://wiki.sagemath.org/SupportedPlatforms)

We currently have the situation that Sage will not build with the latest gcc. That's both the current version of Sage (4.6.2) and I suspect 4.7 will not build either, since there's no progress to my knowledge on the Singular issue - see #11084, although that has been reported upstream.

Dave

comment:24 Changed 10 years ago by jdemeyer

PARI does not build with:

  1. gcc 4.4.1 (#10120)
  2. gcc 4.5.1 on Itanium (#9897, http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46044)

Changed 10 years ago by drkirkby

Suggest use of recent gcc. Drop mention of gcc 4.3.2 being bad.

comment:25 Changed 10 years ago by drkirkby

  • Description modified (diff)

comment:26 Changed 10 years ago by drkirkby

  • Status changed from needs_info to needs_review

comment:27 Changed 10 years ago by drkirkby

OK, I dropped mention of that specific version, and made a general comment to use a recent one, but noted that particular versions have failed on specific platforms.

It would be good if there was a version which worked on every platform.

comment:28 follow-up: Changed 10 years ago by drkirkby

Does anyone feel able to give this a positive review? I'm sure this whole section could be cleaned up further, but I think this is a substantial improvement over what we currently have.

Dave

Changed 10 years ago by jdemeyer

All patches folded

comment:29 Changed 10 years ago by jdemeyer

  • Description modified (diff)

comment:30 in reply to: ↑ 28 ; follow-up: Changed 10 years ago by dimpase

Replying to drkirkby:

Does anyone feel able to give this a positive review? I'm sure this whole section could be cleaned up further, but I think this is a substantial improvement over what we currently have.

Dave

Hi Dave,

tar        (GNU tar, version 1.17 or later)

is not quite right. On MacOSX the tar is a BSD tar:

$ tar --version
bsdtar 2.6.2 - libarchive 2.6.2

Perhaps GNU tar is a Solaris-only requirement...

comment:31 in reply to: ↑ 30 ; follow-up: Changed 10 years ago by dimpase

  • Status changed from needs_review to positive_review

Replying to dimpase:

Replying to drkirkby:

Does anyone feel able to give this a positive review? I'm sure this whole section could be cleaned up further, but I think this is a substantial improvement over what we currently have.

OK, so that tar thing above is the only complaint I can make about the contents. The other thing one might want to think about is how to make this more version-independent, i.e. so that the text does not get obsolete when the current Sage version changes. But I leave it to the next update.

Positive review (assuming the tar comment gets fixed). Dima

comment:32 Changed 10 years ago by jdemeyer

  • Merged in set to sage-4.7.alpha4
  • Resolution set to fixed
  • Status changed from positive_review to closed

comment:33 in reply to: ↑ 31 Changed 10 years ago by drkirkby

Replying to dimpase:

Positive review (assuming the tar comment gets fixed). Dima

Sorry, I missed your "tar" comment, but this now now been merged and closed. I have opened #11159 to address the error about "tar". I'll fix that soon. I believe the number of errors corrected by this update far exceeds the number introduced!

Dave

Note: See TracTickets for help on using tickets.