README: refer to libsecp256k1-dev instead of libsecp256k1-0
#8329
Conversation
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
We don't actually need the development headers, instead using this as a hack to be agnostic to the version scheme and pull in the latest. related: spesmilo#8185 spesmilo#8320 spesmilo#8328 (comment) debian 11 (stable) only has libsecp256k1-0 debian 12 (testing) atm only has libsecp256k1-1 ubuntu 23.04 only has libsecp256k1-1 I expect libsecp256k1-2 might soon get packaged too, now that upstream secp released v0.3.0. So what do we tell users to install? well, turns out most distros have libsecp256k1-dev, which just pulls in the latest secp. Caveat: if there is a new secp release that actually gets packaged on a distro before we can react, then this new instruction will not work.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We don't actually need the development headers, instead using this as a hack to be agnostic to the version scheme and pull in the latest.
related:
#8328 (comment)
#8185
#8320
libsecp256k1-0libsecp256k1-1libsecp256k1-1libsecp256k1-2might soon get packaged too, now that upstream libsecp256k1 released v0.3.0.So what do we tell users to install? well, turns out most distros have
libsecp256k1-dev, which just pulls in the latest secp.Caveat: if there is a new secp release that actually gets packaged on a distro before we can react, then this new instruction will not work.
I think we should similarly update the website:
https://github.com/spesmilo/electrum-web/blob/58755abe49fcbcf295aed67ae3c3d52c1902b07b/panel-download.html.template#L126