mirror/vcpkg
1
0
Fork 0
mirror of https://github.com/microsoft/vcpkg.git synced 2024-12-04 03:01:39 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

[libsodium] Add comment about tag usage (#39388)

Browse Source
This commit is contained in:
martingalvan-volue 2024-06-20 20:38:00 +02:00 committed by GitHub
parent 7e99074c28
commit bc104c8f14
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 14 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ports/libsodium/portfile.cmake
View File

@ -1,3 +1,8 @@
# libsodium has a special branching/tagging scheme, where regular version tags can actually be moved
# as new patches are applied to that version. This means that we may get unexpected hash mismatches
# when the upstream tag points to a new commit. To avoid this, we must make sure that we always
# use a '-RELEASE' tag, since those seem to be fixed to a single commit.
# See https://github.com/jedisct1/libsodium/issues/1373#issuecomment-2135172301 for more info.
vcpkg_from_github(
OUT_SOURCE_PATH SOURCE_PATH
REPO jedisct1/libsodium

2
ports/libsodium/vcpkg.json
View File

@ -1,7 +1,7 @@
{
"name": "libsodium",
"version": "1.0.20",
"port-version": 2,
"port-version": 3,
"description": "A modern and easy-to-use crypto library",
"homepage": "https://libsodium.org/",
"license": "ISC",

2
versions/baseline.json
View File

@ -4978,7 +4978,7 @@
},
"libsodium": {
"baseline": "1.0.20",
"port-version": 2
"port-version": 3
},
"libsonic": {
"baseline": "0.2.0",

5
versions/l-/libsodium.json
View File

@ -1,5 +1,10 @@
{
"versions": [
{
"git-tree": "6dcb750702485c4dafac0b605b910b81e2c48831",
"version": "1.0.20",
"port-version": 3
},
{
"git-tree": "1b7b00b7cccd397e07fa2b1b3ce3725d3ebead29",
"version": "1.0.20",