[cpr] update to 1.10.2

[Adela0814]

Fixes #30725
Tested all feature in the following triplets:

• x64-windows
• x64-windows-static
• x86-windows

• Changes comply with the maintainer guide
• SHA512s are updated for each updated download
• The "supports" clause reflects platforms that may be fixed by this new version
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[Adela0814]

Include upstream fixes: libcpr/cpr@1e83539 and libcpr/cpr@025984a.

[dg0yt]

Actually it is not exactly 1.10.2 but 1.10.2+3.

[Adela0814]

What does 1.10.2+3 mean? Do you mean the version should be version+commitid?

[dg0yt]

In this way, it would indicate:

• It is not 1.10.2. (true!)
• It is newer than 1.10.2 but older than 1.10.3 (indicated by +).
• It is three commits more (indicated by 3).

Commit IDs cannot be compared for "newer". We need dates (20230418) or number of commits (3) or numbered identifers (patch3).

I don't know if the + syntax is supported by the version-semver scheme, but it is by the version scheme.

[BillyONeal]

• in semver world means "build metadata" and is not semantically relevant. I'm going to include it here because the build is green and the change is otherwise good but I don't think this establishes convention.

[dg0yt]

In repology world 1.10.2 means 1.10.2, and using anything but the corresponding tarball means "lying about the version".

[BillyONeal]

Thanks for the update!

[GlassBil]

cpr 1.10.x has cpp17 as min c++ standard. Any way to use 1.9.x (which is still maintained until 2025) for systems that don't support cpp17? Rather not lock builtin-baseline to a commit before this update.

[dg0yt]

cpr 1.10.x has cpp17 as min c++ standard. Any way to use 1.9.x (which is still maintained until 2025) for systems that don't support cpp17? Rather not lock builtin-baseline to a commit before this update.

In manifest mode, you don't need to lock the baseline. You can use overrides to pin specific port versions:
https://learn.microsoft.com/en-us/vcpkg/users/versioning#overrides

[GlassBil]

In manifest mode, you don't need to lock the baseline. You can use overrides to pin specific port versions: https://learn.microsoft.com/en-us/vcpkg/users/versioning#overrides

Unfortunately, you can't use overrides without builtin-baseline:

error: vcpkg.json was rejected because it uses "overrides" and does not have a "builtin-baseline". This can be fixed by removing the uses of "overrides" or adding a "builtin-baseline".

[dg0yt]

What I meant was that you can set the baseline to a recent commit. You don't need to lock everything to the old state.