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

Change sage -p to always behave like sage -p -f #19116

Closed
jdemeyer opened this issue Aug 31, 2015 · 24 comments
Closed

Change sage -p to always behave like sage -p -f #19116

jdemeyer opened this issue Aug 31, 2015 · 24 comments

Comments

@jdemeyer
Copy link

Now that we have #19101, we should change sage -p (the low-level command to install a single package) to stop checking whether the package is already installed: all dependency checking should be moved to build/make/Makefile, used by sage -i.

Component: scripts

Author: Jeroen Demeyer

Branch/Commit: 6a1d76b

Reviewer: Travis Scrimshaw

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

@jdemeyer jdemeyer added this to the sage-6.9 milestone Aug 31, 2015
@jdemeyer
Copy link
Author

Dependencies: #19101

@jdemeyer
Copy link
Author

@jdemeyer
Copy link
Author

New commits:

31ff6e7Parse sage-spkg options in sage-spkg
cb05746Add sage --location option to run sage-location
e856a8eChange sage -i to install with dependencies
93ec09bChange sage -p to always install a package

@jdemeyer
Copy link
Author

Commit: 93ec09b

@tscrim
Copy link
Collaborator

tscrim commented Aug 31, 2015

comment:4

If -p is to always force a reinstall, then it doesn't behave the same as -i (and if I read your changes correctly, -p does not support the -f option). Would you be opposed to being explicit about -p and the options it supports in advanced?

@jdemeyer
Copy link
Author

comment:5

Replying to @tscrim:

If -p is to always force a reinstall, then it doesn't behave the same as -i

Of course not. We wouldn't have two -i and -p options if they behaved the same.

I'll think about your "help" suggestion.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Aug 31, 2015

Changed commit from 93ec09b to c6ddd0e

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Aug 31, 2015

Branch pushed to git repo; I updated commit sha1. New commits:

c6ddd0eBetter help

@tscrim
Copy link
Collaborator

tscrim commented Aug 31, 2015

comment:7

Thanks.

@tscrim
Copy link
Collaborator

tscrim commented Aug 31, 2015

Reviewer: Travis Scrimshaw

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Sep 1, 2015

Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. New commits:

f3d7ef3Remove -f option to sage-spkg when running sage -i

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Sep 1, 2015

Changed commit from c6ddd0e to f3d7ef3

@jdemeyer
Copy link
Author

jdemeyer commented Sep 1, 2015

comment:9

I forgot an important and obviously needed fix. I hope the positive_review can stand.

@vbraun
Copy link
Member

vbraun commented Sep 2, 2015

@vbraun
Copy link
Member

vbraun commented Sep 4, 2015

@vbraun
Copy link
Member

vbraun commented Sep 4, 2015

comment:11

Reopening because of #19104

@vbraun vbraun reopened this Sep 4, 2015
@jdemeyer
Copy link
Author

jdemeyer commented Sep 5, 2015

Changed dependencies from #19101 to #19101, #19104

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Sep 5, 2015

Changed commit from f3d7ef3 to 6a1d76b

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Sep 5, 2015

Branch pushed to git repo; I updated commit sha1. New commits:

4eb1aa8Restore SAGE_INSTALL_FETCH_ONLY support
6a1d76bMerge #19104

@jdemeyer
Copy link
Author

comment:18

Thanks! I am making this a blocker because it is an important user interface change which is best merged in the same release as #19101.

@tscrim
Copy link
Collaborator

tscrim commented Sep 10, 2015

comment:19

Sorry for taking so long to get back to this. However there seems to be a conflict with the latest beta.

@jdemeyer
Copy link
Author

comment:20

Replying to @tscrim:

Sorry for taking so long to get back to this. However there seems to be a conflict with the latest beta.

It merges cleanly for me...

@jdemeyer
Copy link
Author

Changed dependencies from #19101, #19104 to none

@vbraun
Copy link
Member

vbraun commented Sep 11, 2015

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