-
-
Notifications
You must be signed in to change notification settings - Fork 480
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
Handle SAGE_CHECK_PACKAGES in build/make/Makefile.in, not sage-spkg #30118
Comments
New commits:
|
This comment has been minimized.
This comment has been minimized.
Commit: |
Author: Matthias Koeppe |
This comment has been minimized.
This comment has been minimized.
comment:5
Marking it as critical as it is needed for CI testing of blocker package upgrade ticket #29766 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
Merged current beta, needs review |
Reviewer: Dima Pasechnik |
comment:9
looks good as refactoring. |
comment:10
Thanks! |
comment:11
Yes, I'm already using this in various test runs. |
Changed branch from u/mkoeppe/handle_sage_check_packages_in_build_make_makefile_in__not_sage_spkg to |
#29766, #29441, and #29497 introduce build dependencies for packages that are only active when
SAGE_CHECK
is notno
.But whether a package needs its check-dependencies depends on both
SAGE_CHECK_PACKAGES
andSAGE_CHECK
.In this ticket, we move the handling of
SAGE_CHECK_PACKAGES
fromsage-spkg
to the Makefile.This allows packages to conditionalize dependencies based on the new makefile variables
SAGE_CHECK_symengine_py
(for #29497) etc.CC: @jhpalmieri @orlitzky @kliem @kiwifb
Component: build
Author: Matthias Koeppe
Branch/Commit:
5d13238
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/30118
The text was updated successfully, but these errors were encountered: