-
-
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 DESTDIR support for gap #25044
Comments
comment:2
Why not use |
comment:3
Hmm, for some reason I thought it wasn't a standard autoconf configure, but it looks like it is, actually. I don't know why it's being passed some |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
(already merges without conflict with #23733) |
comment:6
This appears to have some kind of problem installing |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Work Issues: merge conflicts |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:12
I think it should be good now. |
Changed work issues from merge conflicts to none |
comment:13
I believe this issue can reasonably be addressed for Sage 8.4. |
comment:14
Since
by
|
comment:15
I would remove
You have a commit message Given that we have
(just a question, if there is a good reason to keep it there: fine for me) |
comment:17
Replying to @jdemeyer:
Yes, this ticket just predates that being merged; as long as this is still open it makes sense to go ahead and move that stuff into an spkg-legacy-uninstall. |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
comment:19
Done all of the above. |
comment:20
Bump. |
comment:22
This is also implemented by #22626 which supersedes this. |
Implements #24024 for gap; this one is slightly non-trivial.
Depends on #24599
Depends on #25039
Depends on #23733
Component: build
Keywords: destdir gap
Author: Erik Bray
Branch/Commit: u/embray/build/destdir-gap @
ee25fe7
Issue created by migration from https://trac.sagemath.org/ticket/25044
The text was updated successfully, but these errors were encountered: