-
-
Notifications
You must be signed in to change notification settings - Fork 491
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 support for staged installations in packages that use sdh_pip_install #24646
Comments
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:5
merge failure on 8.3.b0 |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:7
Rebased since its dependency #24645 has been satisfied. |
Changed dependencies from #24645 to none |
comment:8
What's up with |
comment:9
For
It seems like a useful sanity check. |
comment:10
Replying to @jdemeyer:
Let me check whether or not that was intended to be in this branch.
I don't see how you can assert that without knowing what it is. |
comment:11
Replying to @jdemeyer:
You can see just above that it checks that the directory being symlinked exists before making the symlink. |
comment:12
Replying to @embray:
It's not at all obvious to me that the check before is equivalent to the |
comment:13
Replying to @embray:
I know what it is because I wrote the original. The code which is in that |
comment:14
I see, you even removed the |
Reviewer: Julian Rüth |
comment:29
See patchbot |
comment:30
Apparently I had asked Jeroen to make this a prerequisite to #24935 (after all, this ticket was opened first and had no reason to wait so long to be merged). But he forgot about that or ignored it (and I likewise forgot about it). |
comment:32
The |
comment:33
I believe this issue can reasonably be addressed for Sage 8.4. |
comment:34
You obviously didn't try to build Sage with the ticket
|
comment:35
Replying to @vbraun:
That's a bit flippant. Of course I built Sage with this ticket. It's been opened for 6 months and has had to be rebased many times. Perhaps there was a small merge error along the way. But that's not as if it was never tested... |
comment:36
Also, the ticket doesn't bump the package versions of the affected packages, so you would only see the issue if rebuilding from scratch. The "obviously" is pretty unnecessary. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Changed branch from u/embray/build/destdir-pip to |
This implements #22509 for any Python packages that are installed with
sdh_pip_install
. Passing--root=
to pip is essentially the same as usingDESTDIR
withmake install
.This required a few additional changes to a small handful of packages for them to work with staged installation.
Component: build
Author: Erik Bray
Branch/Commit:
ff1ccd3
Reviewer: Julian Rüth
Issue created by migration from https://trac.sagemath.org/ticket/24646
The text was updated successfully, but these errors were encountered: