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
Add option "-c" to sage-spkg to run the test-suite #12613
Comments
This comment has been minimized.
This comment has been minimized.
Attachment: trac_12613-doc.patch.gz Sage library |
comment:2
Will this also work with |
comment:3
Never mind, I should have read the patches first! |
comment:4
The doc seems correct and appropriately formatted (I hadn't seen |
comment:5
wouldn't work since it would make SAGE_CHECK_PACKAGES equal to !python. So better set
or something. Also, it conflicts with #12602. |
comment:6
Replying to @jdemeyer:
Good point. Fixed.
Well, I didn't list #12602 as a prerequisite ;) I'm attaching two versions of the patch, one which depends on #12602, and one which doesn't. (I don't know if I'll be able to review #12602 any time soon, by the way.) |
Attachment: trac_12613-root.post12602.patch.gz |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Reviewer: Jeroen Demeyer |
This comment has been minimized.
This comment has been minimized.
comment:9
John, I added two reviewer patches. If you're happy with my patches, you can set positive review. |
comment:10
Do you think it's clear enough that you can add the options diff --git a/spkg/bin/sage b/spkg/bin/sage
--- a/spkg/bin/sage
+++ b/spkg/bin/sage
@@ -113,12 +113,17 @@ usage_advanced() {
#### |.....................--.|...................................................|
echo "Installing packages and upgrading:"
echo " -experimental -- list all experimental packages that can be installed"
- echo " -f [packages] -- force build of the given Sage package (even if it is"
- echo " already installed)"
- echo " -f -s [packages] -- like -f but do not delete the spkg/build directories"
- echo " -i [packages] -- install the given Sage packages"
- echo " if no packages given, print a list of all installed"
- echo " -i -s [packages] -- like -i but do not delete the spkg/build directories"
+ echo " -f [packages] -- shortcut for -i -f: force build of the given Sage"
+ echo " packages."
+ echo " -i [options] [packages]"
+ echo " -- install the given Sage packages (unless they are"
+ echo " already installed); if no packages are given, print"
+ echo " a list of all installed packages. Options:"
+ echo " -c -- run the packages' test suites"
+ echo " -f -- force build: install the packages even"
+ echo " if they are already installed"
+ echo " -s -- do not delete the spkg/build directories"
+ echo " after a successful build"
echo " -optional -- list all optional packages that can be installed"
echo " -standard -- list all standard packages that can be installed"
#echo " -update -- download latest non-optional Sage packages (do not build them)" I can provide a patch for this and a similar one for the reference manual if you want me to. |
Attachment: 12613_review.patch.gz |
Attachment: 12613_review_doc.patch.gz |
comment:11
I did those changes, needs_review. |
comment:12
Great, looks good. |
Merged: sage-5.0.beta13 |
With the attached patches, running
sage -i -c <pkg>
orsage -i --check <pkg>
will install the package and then run its test suite, regardless of the setting ofSAGE_CHECK
orSAGE_CHECK_PACKAGES
.Apply
Depends on #12479
Depends on #12579
Depends on #12602
CC: @jdemeyer
Component: build
Author: John Palmieri
Reviewer: Jeroen Demeyer
Merged: sage-5.0.beta13
Issue created by migration from https://trac.sagemath.org/ticket/12613
The text was updated successfully, but these errors were encountered: