libsodium-go
libsodium-go copied to clipboard
Backward compatiblity?
How should we handle multiple libsodium versions? Do we even care?
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:
- Add wrappers for newer functionality to separate files and use build tags. This creates quite a bit of clutter.
- Only update the required libsodium version on minor releases (so dependencies can use https://gopkg.in).
- Aim to replace the libsodium dependency by native functionality altogether.
I think the second option is the way to go, as it would be easier for development.
Push for the 2nd option, people should keep their libraries updated or they can freeze them in their repos.