#20189: Update docs for new 'typical' dmg
----------------------------------+------------------------
Reporter: kcrisman | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-7.1
Component: user interface | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
----------------------------------+------------------------
Comment (by kcrisman):
On behalf of mgoerner, who apparently is having login problems on Trac:
----
These comments are still correct, but awkward explaining something that is
self-explanatory, probably better to omit the "Installation" paragraph all
together.
Just some more thoughts:
It would be better if we actually split the one long README file into two,
one for each distribution type and change the Makefiles so that the
relevant README file is copied to the root level of the dmg. That way we
can get rid off the part of the introduction saying to which paragraph the
reader should jump to.
There is some stuff that we can probably prune:
* Information about OS X 10.4 - I don't think a lot of people are using
10.4 at this point. Do recent sage's even run on OS X 10.4?
* The comment that one should use "cp -r ..." if finder can't copy it. I
never ran into this. Is this still relevant?
* "Select run it with Terminal"... It seems to me that in the last couple
of versions of OS X finder does this automatically. If someone has old OS
X versions around, it would be great if we could see when this is actually
needed. Ideally, we could create a .DS_Store file in the sage directory
that tells finder to run sage in a terminal on old OS X finder's.
* "sage -bdist" - is now obsolete, see
http://trac.sagemath.org/ticket/19673 - should such information be in a
README file for users? Seems better suited we put such comments about the
build process in, e.g., src/mac-app/Makefile.
Other thoughts:
- consistently 80 chars per line
- consistent formatting
And finally: '''Do we even need two different distributions .app.dmg and
.dmg? Isn't the .app.dmg just enough?'''
The filesize is pretty much exactly the same so that is not an argument.
And with the symlink to the sage binary I added in
http://trac.sagemath.org/ticket/20119, I wonder whether it is discoverable
enough now for users who want to use it from the command line (maybe add a
comment to the README?).
--
Ticket URL: <http://trac.sagemath.org/ticket/20189#comment:5>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
