Remove most spkg-legacy-uninstall scripts#36839
Merged
vbraun merged 26 commits intosagemath:developfrom Dec 19, 2023
Merged
Conversation
These are pretty obvious: run "git grep -i cygwin build/bin" and then delete the special cases for Cygwin.
SageMath version 10.3.beta1, Release Date: 2023-12-10
…those commands into spkg-legacy-uninstall scripts
e42f181 to
77c6c04
Compare
Member
|
this probably needs non-incremental testing, to see that all this pkg-config magic still works |
|
Documentation preview for this PR (built with commit 77c6c04; changes) is ready! 🎉 |
Contributor
Author
Member
is this something to happen once only, or a real bug? |
Contributor
Author
|
Where do you see this? In a local test or in one of the CI runs? |
Member
https://github.com/sagemath/sage/actions/runs/7171776285/job/19527492807?pr=36862 |
Contributor
Author
|
I think that's unrelated noise in the Conda CI |
Contributor
Author
|
So let's get this in? |
Member
|
local tests seem OK. |
Member
|
Is there a conflict with #36778 ? |
Contributor
Author
|
#36778 is already merged here |
Member
|
ah, right |
dimpase
approved these changes
Dec 13, 2023
Contributor
Author
|
Thanks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Most normal SPKGs are installed by staging in
DESTDIR. When copying to the final install location inSAGE_LOCAL, an installation record is created, which is used later in package uninstallation.However, when SPKG installation was switched to using staging in
DESTDIR(Meta-ticket #24024), the parts ofspkg-installscripts that used to be responsible for removing an old version of the installed package were either kept in place or moved tospkg-legacy-uninstallscripts. This was done to enable incremental builds from older installations.By passage of time, this is no longer needed.
Some of the removals are a partial cherry-pick from #25140 by @embray.
We also switch
frobbytoDESTDIRstaging and add anspkg-legacy-uninstallscript.Resolves #25140.
Resolves #30480.
📝 Checklist
⌛ Dependencies