Automatic port update script for vcpkg

[Neumann-A]

@jiayuehua:
Since you did a lot of port updates in vcpkg you probably used a script for the update.
Is that script somewhere publically available?
I remember somebody posting a script somewhere but it is bascially impossible to find

[jiayuehua]

yes I am using a bash script that I wrote last october. I will share with you later today.

[jiayuehua]

https://github.com/jiayuehua/studyNote/tree/main/vcpkg%20brutal%20update%20port This is the port update script I use.

[Neumann-A]

Ah okay. You still manually provide the new values. I was looking for something which checks upstream if a new tag is available and then updates the values.

[m-kuhn]

this: https://gist.github.com/lukechilds/a83e1d7127b78fef38c2914c4ececc3c ?

[m-kuhn]

Also interesting: https://github.com/msclock/cmake-registry/blob/master/.github/renovate.json by @msclock

[msclock]

It relies on Renovate to check the preset upstream tag or branch hash in vcpkg.json for automatic updates, and then updates the port and version through CI.

I have mentioned it in microsoft/vcpkg#34710.

[m-kuhn]

@msclock did you look into updating the sha as well?

[msclock]

I don't understand clearly what's the sha.🤔 But if it it about the git hash on the special branch, I do detect it because some reports doesn't use semver to tag or release their codebases.

[m-kuhn]

Normally you'll need to update two things:

1. the version (git tag) in vcpkg.json
2. the sha512 of the downloaded file in portfile.cmake

Random example here https://github.com/microsoft/vcpkg/blob/master/ports/exiv2/portfile.cmake#L5

And a rough way to detect it by launching vcpkg executable and parsing the output can be seen in https://github.com/jiayuehua/studyNote/blob/main/vcpkg%20brutal%20update%20port/fix-sha

[msclock]

I handled the sha512 in port files within GitHub actions, see https://github.com/msclock/cmake-registry/blob/8169c0dce40d078aef52a54bf909ffdfcda210e3/.github/workflows/ci.yml#L76