fix up drakma for LispWorks 8.0 #129
Open
Conversation
This file contains 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
|
This is a minimally-invasive fix vs. some of the other PRs looking to do the same. |
|
I can confirm this PR works on macOS Sonoma 14.2.1 with LispWorks 8. |
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.
This change fixes up the LispWorks checks that were looking for LispWorks 7.1 to look for LispWorks 7+, fixing drakma for LispWorks 8.x.
Tested against LW8.0 (macOS Ventura 13.1 arm64), LW7.1 (as much as possible under macOS 13.1 arm64, changes to SSL libs make that challenging), sbcl 2.2.10 (macOS 13.1 arm64).