Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify how/where to install optional packages #16628

Closed
kcrisman opened this issue Jul 8, 2014 · 6 comments
Closed

Clarify how/where to install optional packages #16628

kcrisman opened this issue Jul 8, 2014 · 6 comments

Comments

@kcrisman
Copy link
Member

kcrisman commented Jul 8, 2014

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.)

Component: documentation

Reviewer: Jeroen Demeyer

Issue created by migration from https://trac.sagemath.org/ticket/16628

@kcrisman kcrisman added this to the sage-6.3 milestone Jul 8, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@jdemeyer
Copy link

comment:2

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

./sage -i package_name

@jdemeyer
Copy link

comment:3

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

@kcrisman
Copy link
Member Author

kcrisman commented Sep 2, 2014

comment:4

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.

@jdemeyer
Copy link

jdemeyer commented Sep 2, 2014

comment:5

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".

@kcrisman
Copy link
Member Author

kcrisman commented Sep 2, 2014

comment:6

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.

@jdemeyer jdemeyer removed this from the sage-6.4 milestone Sep 7, 2015
@jdemeyer
Copy link

jdemeyer commented Sep 7, 2015

Reviewer: Jeroen Demeyer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants