Opened 7 years ago

Closed 6 years ago

#16628 closed defect (fixed)

Clarify how/where to install optional packages

Reported by: kcrisman Owned by:
Priority: minor Milestone: sage-duplicate/invalid/wontfix
Component: documentation Keywords:
Cc: Merged in:
Authors: Reviewers: Jeroen Demeyer
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges


This is currently a ridiculous situation. Some packages are only available in 'old-style', but 'new-style' ones aren't installable (as far as I can tell) with a single command sage -do_this. The install guide still uses the sage -i syntax (which makes a lot of sense to me) and there is no place the new procedure is documented, not really even in the developer guide, though people shouldn't have to look at that to (say) install the small groups package. (And it wouldn't hurt to add some FAQ somewhere, or a nice test in a very visible place for groups, about that, as it keeps getting asked.)

Change History (10)

comment:1 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:2 Changed 7 years ago by jdemeyer

I don't understand the problem here, can you please clarify? Both old and new packages can be installed using

./sage -i package_name

comment:3 Changed 7 years ago by jdemeyer

There is an issue with optional packages, namely that only lists the old packages, but that doesn't seem to be what this ticket is about...

comment:4 Changed 7 years ago by kcrisman

Well, at any rate I have personally had trouble installing new-style optional spkgs with sage -i when there is an older version still up on the old packages list. I cannot now remember precisely which ones. I've always ended up having to put stuff in upstream/ first.

comment:5 Changed 7 years ago by jdemeyer

In general, ./sage -i package should work both for old and new packages. It could of course be that there is a problem with a specific package or that somewhere, there is bad documentation for a specific package. Therefore, this ticket should either be made more concrete or closed as "invalid".

comment:6 Changed 7 years ago by kcrisman

I'm sorry I don't have more specific info today. I hope I won't have to open another ticket like this, but I guess you can close it.

comment:7 Changed 6 years ago by jdemeyer

  • Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

comment:8 Changed 6 years ago by jdemeyer

  • Status changed from needs_review to positive_review

comment:9 Changed 6 years ago by jdemeyer

  • Reviewers set to Jeroen Demeyer

comment:10 Changed 6 years ago by vbraun

  • Resolution set to fixed
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.