update installation guide
videlec opened this issue · 49 comments
Update the instructions in the installation guide
- remove outdated information
- mention the cygwin windows binaries
- mention package manager installation: Debian >= 9, Ubuntu >= 18.04, archlinux, Fedora >= 27, ... (see https://wiki.sagemath.org/Distribution)
- get rid of
src/bin/sage-README-osx.txtand instead move its content in the installation guide in order to have clear OS X explanations (ie what to choose betweentar.gz,app.dmgordmgand do we deal with them). - quick command line howto (ie
sageandsage -n) and pointers to do the first steps in Sage - mention Docker
- mention conda
- mention NixOS
Some possibilities
- mention the brew install (see https://groups.google.com/d/msg/sage-devel/jdLfIKQ1M18/PVQqJUUqAgAJ)?
- mention the distribution specifics:
CC: @slel
Component: documentation
Author: Vincent Delecroix
Branch/Commit: aa02464
Reviewer: Julian Rüth
Issue created by migration from https://trac.sagemath.org/ticket/25995
Author: Vincent Delecroix
Description changed:
---
+++
@@ -1,5 +1,7 @@
Update the instructions in the installation guide
+- remove outdated information
- mention the cygwin windows binaries
- mention package manager installation (Debian >= 9, Ubuntu >= 18.04, archlinux)
- clearer explanations for OS X (what to choose between `tar.gz`, `app.dmg` or `dmg`)
+- quick command line start (ie `sage` and `sage -n`)Branch: u/vdelecroix/25995
Description changed:
---
+++
@@ -2,6 +2,6 @@
- remove outdated information
- mention the cygwin windows binaries
-- mention package manager installation (Debian >= 9, Ubuntu >= 18.04, archlinux)
-- clearer explanations for OS X (what to choose between `tar.gz`, `app.dmg` or `dmg`)
+- mention package manager installation: Debian >= 9, Ubuntu >= 18.04, archlinux, Fedora, ... (see https://wiki.sagemath.org/Distribution)
+- clearer explanations for OS X (what to choose between `tar.gz`, `app.dmg` or `dmg`) and mention the possible brew install (see https://groups.google.com/d/msg/sage-devel/jdLfIKQ1M18/PVQqJUUqAgAJ)
- quick command line start (ie `sage` and `sage -n`)Description changed:
---
+++
@@ -2,6 +2,7 @@
- remove outdated information
- mention the cygwin windows binaries
-- mention package manager installation: Debian >= 9, Ubuntu >= 18.04, archlinux, Fedora, ... (see https://wiki.sagemath.org/Distribution)
+- mention package manager installation: Debian >= 9, Ubuntu >= 18.04, archlinux, Fedora >= 27, ... (see https://wiki.sagemath.org/Distribution)
- clearer explanations for OS X (what to choose between `tar.gz`, `app.dmg` or `dmg`) and mention the possible brew install (see https://groups.google.com/d/msg/sage-devel/jdLfIKQ1M18/PVQqJUUqAgAJ)
-- quick command line start (ie `sage` and `sage -n`)
+- mention the various docker images around
+- quick command line howto (ie `sage` and `sage -n`) and pointers to do the first steps in Sage+OS X dmg
+--------
+
+A possible alternive on OS X is to use ``app.dmg`` or ``dmg`` files. Such
+installation will automtically create shortcuts on your desktops. Simply
+follow the section "Download Guide" above and download the ``dmg`` file
+corresponding to your system.
+
+TO BE FINISHED
And earlier you also have something about which one is best. There is a separate readmeosx file somewhere which will answer many of your questions here; the short version is that app.dmg is better for those wanting a GUI, dmg is better for those only wanting command line access. tar.gz is definitely not preferred for mac
Replying to @kcrisman:
+OS X dmg +-------- + +A possible alternive on OS X is to use ``app.dmg`` or ``dmg`` files. Such +installation will automtically create shortcuts on your desktops. Simply +follow the section "Download Guide" above and download the ``dmg`` file +corresponding to your system. + +TO BE FINISHEDAnd earlier you also have something about which one is best. There is a separate readmeosx file somewhere which will answer many of your questions here; the short version is that app.dmg is better for those wanting a GUI, dmg is better for those only wanting command line access. tar.gz is definitely not preferred for mac
The only README.txt I found is on the sagemath website when going to "Download" and then "Mac OSX". It does not tell anything about the three different format of installation.
Searching the Sage repo on GitHub for "readme":
reveals three files
The last one might the one kcrisman has in mind.
Oops, I missed some. Searching again for "mac"
I found these two too:
Description changed:
---
+++
@@ -3,6 +3,7 @@
- remove outdated information
- mention the cygwin windows binaries
- mention package manager installation: Debian >= 9, Ubuntu >= 18.04, archlinux, Fedora >= 27, ... (see https://wiki.sagemath.org/Distribution)
-- clearer explanations for OS X (what to choose between `tar.gz`, `app.dmg` or `dmg`) and mention the possible brew install (see https://groups.google.com/d/msg/sage-devel/jdLfIKQ1M18/PVQqJUUqAgAJ)
+- get rid of `src/bin/sage-README-osx.txt` and instead move its content in the installation guide in order to have clear OS X explanations (ie what to choose between `tar.gz`, `app.dmg` or `dmg` and do we deal with them).
+- should we mention the brew install (see https://groups.google.com/d/msg/sage-devel/jdLfIKQ1M18/PVQqJUUqAgAJ)?
- mention the various docker images around
- quick command line howto (ie `sage` and `sage -n`) and pointers to do the first steps in SageThanks Samuel! It is definitely src/bin/sage-README-osx.txt and this file will be removed by this ticket (or more precisely, replace its content with "go read the installation manual").
Whoah Nelly! But note that that file actually shows up in the dmg created (if you open it it appears in a nice Mac-specific Finder way). So be careful about this, and be sure to have someone test with a Mac on a app dmg, possibly also regular dmg.
Ready for a relecture!
Description changed:
---
+++
@@ -4,6 +4,8 @@
- mention the cygwin windows binaries
- mention package manager installation: Debian >= 9, Ubuntu >= 18.04, archlinux, Fedora >= 27, ... (see https://wiki.sagemath.org/Distribution)
- get rid of `src/bin/sage-README-osx.txt` and instead move its content in the installation guide in order to have clear OS X explanations (ie what to choose between `tar.gz`, `app.dmg` or `dmg` and do we deal with them).
-- should we mention the brew install (see https://groups.google.com/d/msg/sage-devel/jdLfIKQ1M18/PVQqJUUqAgAJ)?
+- quick command line howto (ie `sage` and `sage -n`) and pointers to do the first steps in Sage
+
+Some possibilities
+- mention the brew install (see https://groups.google.com/d/msg/sage-devel/jdLfIKQ1M18/PVQqJUUqAgAJ)?
- mention the various docker images around
-- quick command line howto (ie `sage` and `sage -n`) and pointers to do the first steps in SageDescription changed:
---
+++
@@ -9,3 +9,5 @@
Some possibilities
- mention the brew install (see https://groups.google.com/d/msg/sage-devel/jdLfIKQ1M18/PVQqJUUqAgAJ)?
- mention the various docker images around
+- mention the distribution specifics:
+ - [Archlinux](https://wiki.archlinux.org/index.php/SageMath)This content of this file has been moved to the installation guide. That's not correct, is it? It has been moved to the mac-app README hasn't it? Should we just delete this file?
Changed branch from u/vdelecroix/25995 to u/saraedum/25995
I added a few more things that I know about. I made quite a few minor changes, mostly related to the correct spelling/casing of trademarks and fixed some sentences that I stumbled upon.
Something that I am still not sure about: Should we consistently call this thing Sage or SageMath? Currently it's still a bit of a mix though I replaced most instances of Sage with SageMath…something that we might want to revert.
Anyway, I don't think we should strive for perfection here. This had already been quite an improvement :)
New commits:
e958968 | Merge remote-tracking branch 'trac/u/vdelecroix/25995' into HEAD |
b7df26f | Fix spelling and grammar |
55d3489 | Mac OS X is now called macOS |
91a9c7e | cygwin is called Cygwin afaik |
4fef756 | archlinux is called Arch Linux |
0a26102 | sagemath is called SageMath |
e6841c9 | Jupyter's notebook is called the Jupyter Notebook afaik |
34f6a7f | OS X is now called macOS |
12997ae | SageMath is also available on NixOS and conda |
d419cc8 | Add conda installation guide |
Description changed:
---
+++
@@ -5,9 +5,11 @@
- mention package manager installation: Debian >= 9, Ubuntu >= 18.04, archlinux, Fedora >= 27, ... (see https://wiki.sagemath.org/Distribution)
- get rid of `src/bin/sage-README-osx.txt` and instead move its content in the installation guide in order to have clear OS X explanations (ie what to choose between `tar.gz`, `app.dmg` or `dmg` and do we deal with them).
- quick command line howto (ie `sage` and `sage -n`) and pointers to do the first steps in Sage
+- mention Docker
+- mention conda
+- mention NixOS
Some possibilities
- mention the brew install (see https://groups.google.com/d/msg/sage-devel/jdLfIKQ1M18/PVQqJUUqAgAJ)?
-- mention the various docker images around
- mention the distribution specifics:
- [Archlinux](https://wiki.archlinux.org/index.php/SageMath)Reviewer: Julian Rüth
Replying to @saraedum:
This content of this file has been moved to the installation guide. That's not correct, is it? It has been moved to the mac-app README hasn't it? Should we just delete this file?
No! This file is distributed together with the macOS applications. You can see that in 25995
diff --git a/src/mac-app/Makefile b/src/mac-app/Makefile
index 3f2dc22..4b8a5b3 100644
--- a/src/mac-app/Makefile
+++ b/src/mac-app/Makefile
@@ -99,7 +99,7 @@ $(TARGET)/Applications:
ln -s /Applications/ $(TARGET)/Applications
# Add the readme file
-$(TARGET)/README.txt: $(SAGE_ROOT)/src/bin/sage-README-osx.txt
+$(TARGET)/README.txt: sage-README-osx.txt
cp $^ $@Changed branch from u/saraedum/25995 to u/vdelecroix/25995
Branch pushed to git repo; I updated commit sha1. New commits:
6b202a4 | fix ReST syntax |
Branch pushed to git repo; I updated commit sha1. New commits:
aa02464 | move linux instructions in a separate file |
I moved the Linux instructions and updated the fact that you absolutely need the documentation (otherwise ? is just broken).
I think this is in good enough shape for now. What do you think?
In the future we might want to update instructions for optional packages (Arch Linux provide some with pacman and pip install does work).
Replying to @videlec:
Replying to @saraedum:
This content of this file has been moved to the installation guide. That's not correct, is it? It has been moved to the mac-app README hasn't it? Should we just delete this file?No! This file is distributed together with the macOS applications. You can see that in
25995diff --git a/src/mac-app/Makefile b/src/mac-app/Makefile index 3f2dc22..4b8a5b3 100644 --- a/src/mac-app/Makefile +++ b/src/mac-app/Makefile @@ -99,7 +99,7 @@ $(TARGET)/Applications: ln -s /Applications/ $(TARGET)/Applications # Add the readme file -$(TARGET)/README.txt: $(SAGE_ROOT)/src/bin/sage-README-osx.txt +$(TARGET)/README.txt: sage-README-osx.txt cp $^ $@
I don't understand. The file in src/bin/ is not distributed with the macOS app anymore. So why do we need it?
Replying to @videlec:
I moved the Linux instructions and updated the fact that you absolutely need the documentation (otherwise
?is just broken).
Sure. It's fine to tell people to install documentation. Note that the ? bug is fixed in #25786 which needs review :).
I think this is in good enough shape for now. What do you think?
Yes, it looks good to me. Have you had a look at the generated HTML?
In the future we might want to update instructions for optional packages (Arch Linux provide some with
pacmanandpip installdoes work).
Sounds good. But let's put this into another ticket.
Replying to @saraedum:
Replying to @videlec:
Replying to @saraedum:
This content of this file has been moved to the installation guide. That's not correct, is it? It has been moved to the mac-app README hasn't it? Should we just delete this file?No! This file is distributed together with the macOS applications. You can see that in
25995diff --git a/src/mac-app/Makefile b/src/mac-app/Makefile index 3f2dc22..4b8a5b3 100644 --- a/src/mac-app/Makefile +++ b/src/mac-app/Makefile @@ -99,7 +99,7 @@ $(TARGET)/Applications: ln -s /Applications/ $(TARGET)/Applications # Add the readme file -$(TARGET)/README.txt: $(SAGE_ROOT)/src/bin/sage-README-osx.txt +$(TARGET)/README.txt: sage-README-osx.txt cp $^ $@I don't understand. The file in
src/bin/is not distributed with the macOS app anymore. So why do we need it?
I tought it was (my modification in the Makefile is just changing the path). I don't have a mac and I will not try to find one to test it. Let me post something on sage-devel.
I can test it on a mac if you want me to.
Replying to @saraedum:
I can test it on a mac if you want me to.
If you have time to do so, please do! See also this post on sage-devel.
I'm not quite sure what the question is here, but here are my comments: first, running make from src/mac-app works for me with this branch. Second, I think you could just delete the (now very small) file src/bin/sage-README-osx.txt, since you've moved the important parts to src/mac-app/, and that's the natural place for that information.
Replying to @jhpalmieri:
I'm not quite sure what the question is here, but here are my comments: first, running
makefromsrc/mac-appworks for me with this branch. Second, I think you could just delete the (now very small) filesrc/bin/sage-README-osx.txt, since you've moved the important parts tosrc/mac-app/, and that's the natural place for that information.
Thanks for checking! Does the sage-README-osx.txt is inside the mac-app produced?
I will delete the one in src/bin following your advice.
The correct README.txt file is produced in the top-level of the .dmg file. (And the tiny sage-README-osx.txt file in src/bin is present in the app, also.)
Hm…I don't see what could possibly break™, but let me try to build it anyway.
Thanks esp. to jhpalmieri for checking out that this all is still working!
Sorry, I can't test this on my macOS as I cannot upgrade to a version that is supports xcode (and I don't want to hack around to install an old xcode.)
Could we set to positive review then?
Great news! Thank you :-)
Changed branch from u/vdelecroix/25995 to aa02464