An inconvenient situation when porting with a custom triplet

[playgithub]

e.g. some lib needs cpp17, so in my own branch of vcpkg

• Add vcpkg\triplets\community\x64-windows-cpp17.cmake
• Add environment variables
  • VCPKG_DEFAULT_HOST_TRIPLET=x64-windows-cpp17
  • VCPKG_DEFAULT_TRIPLET=x64-windows-cpp17

But a port branch should fork from master, which doesn't have vcpkg\triplets\community\x64-windows-cpp17.cmake.
The normal solution is to delete environment variables

• VCPKG_DEFAULT_HOST_TRIPLET
• VCPKG_DEFAULT_TRIPLET
  when porting, add add them back when not porting, it is very inconvenient.

Any better solution?

[playgithub]

A dedicated Windows account for vcpkg is a way.

[Neumann-A]

Use overlay-triplets via VCPKG_OVERLAY_TRIPLETS

[Neumann-A]

also consider moving your triplet out of the vcpkg tree.

[playgithub]

Then env var VCPKG_OVERLAY_TRIPLETS needs to be modified manually instead of VCPKG_DEFAULT_TRIPLET, it seems no more convenient.