We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
How should we handle multiple libsodium versions? Do we even care?
The text was updated successfully, but these errors were encountered:
The main problem I see is that Go doesn't really have any way to handle a build against a different library version. I see three ways of doing it:
I think the second option is the way to go, as it would be easier for development.
Sorry, something went wrong.
Push for the 2nd option, people should keep their libraries updated or they can freeze them in their repos.
No branches or pull requests
How should we handle multiple libsodium versions? Do we even care?
The text was updated successfully, but these errors were encountered: