-
-
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
Install script and pip packages via sage-spkg #29386
Comments
comment:1
pushing these forward to 9.2 |
Dependencies: #29793 |
This comment has been minimized.
This comment has been minimized.
comment:6
+1 this would be a very nice improvement. |
Commit: |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Work Issues: rework on top of #29013 |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
This comment has been minimized.
This comment has been minimized.
Changed work issues from rework on top of #29013 to none |
Changed dependencies from #29013 to none |
This comment has been minimized.
This comment has been minimized.
comment:25
Rebased and dropped all clean/uninstall changes here because that is #29097 |
Work Issues: Move "dummy script package" code to sage-spkg |
…math#29386 The Cython modules depending on optional packages (such as sage.libs.coxeter3) were not being built after sagemath#29386. This showed up in the CI as numerous doctest failures; as reported in sagemath#36775 (comment) Fixed here by avoiding a clash of environment variables that prevented the function `is_package_installed_and_updated` from functioning during the build of sagelib. <!-- ^^^^^ Please provide a concise, informative and self-explanatory title. Don't put issue numbers in there, do this in the PR body below. For example, instead of "Fixes sagemath#1234" use "Introduce new method to calculate 1+1" --> <!-- Describe your changes here in detail --> <!-- Why is this change required? What problem does it solve? --> <!-- If this PR resolves an open issue, please link to it here. For example "Fixes sagemath#12345". --> <!-- If your change requires a documentation PR, please link it appropriately. --> ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> <!-- If your change requires a documentation PR, please link it appropriately --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> <!-- Feel free to remove irrelevant items. --> - [x] The title is concise, informative, and self-explanatory. - [x] The description explains in detail what this PR is about. - [ ] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation accordingly. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on - sagemath#12345: short description why this is a dependency - sagemath#34567: ... --> <!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> URL: sagemath#36900 Reported by: Matthias Köppe Reviewer(s): Dima Pasechnik
Follow-up from #29287.
Script packages are installed by special rules in
build/make/Makefile
.This ticket installs them by
sage-spkg
instead. This enables script packages to participate in the staged installs (SAGE_DESTDIR
) and uninstallation mechanisms.This is useful for #29387 to clean up #27870/#29003/#29082, which introduced files in
SAGE_LOCAL
that do not belong to any package and are never uninstalled.We also make the decision whether
spkg-install
is generated from a templatespkg-install.in
or provided as is in the source tree orthogonal to the distinctionsource=script
vs.source=pip
.We simply generate
spkg-install
ifspkg-install.in
is present.Ideally, when done, changing a package's source between script and normal and pip will no longer require running
bootstrap
.CC: @dimpase @jhpalmieri @embray @orlitzky
Component: build
Work Issues: Move "dummy script package" code to sage-spkg
Author: Matthias Koeppe
Branch/Commit: u/mkoeppe/install_script_packages_via_sage_spkg @
7a25d1d
Issue created by migration from https://trac.sagemath.org/ticket/29386
The text was updated successfully, but these errors were encountered: