Merge pull request #1 from vegastrike/sgt_2023-11-23

Merging Upstream Changes 2023-11-23

.github/workflows/check_issues.yml

@@ -6,7 +6,7 @@ on:
       - opened
 
 jobs:
-  missing-windows-sdk-issue:
+  check-for-common-issues:
     runs-on: ubuntu-latest
     permissions:
       issues: write
@@ -20,6 +20,8 @@ jobs:
               repo: context.repo.repo
             };
             let issue = await github.rest.issues.get(issue_query)
+
+            // missing-windows-sdk-issue
             let reg = /RC Pass 1: command "rc .*" failed \(exit code 0\) with the following output:/;
             if (reg.test(issue.data.body)){
               await github.rest.issues.removeAllLabels(issue_query);
@@ -30,3 +32,13 @@ jobs:
               await github.rest.issues.createComment({...issue_query, body}); 
               // Close the issue? 
             }
+
+            // msys2 download fails => old vcpkg version
+            reg = /error: https:\/\/repo\.msys2\.org\/.*: failed: status code 404/;
+            if (reg.test(issue.data.body)){
+              await github.rest.issues.removeAllLabels(issue_query);
+              await github.rest.issues.setLabels({...issue_query, labels: ["category:question"]});
+              let body = "Try updating your vcpkg version via `git pull` to resolve this issue. MSYS2 downloads are removed from the upstream servers from time to time, so using an up-to-date vcpkg version is necessary."
+              await github.rest.issues.createComment({...issue_query, body}); 
+              // Close the issue? 
+            }

.github/workflows/stale.yml

@@ -10,22 +10,22 @@ jobs:
       - uses: actions/stale@v6
         with:
           stale-issue-message: 'This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.'
-          only-labels: 'category:question'
+          any-of-labels: 'category:question,requires:repro,requires:more-information'
           days-before-issue-stale: 28
           days-before-pr-stale: -1
           days-before-close: 14
       - uses: actions/stale@v6
         with:
-          stale-issue-message: 'This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 28 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment.'
-          only-labels: 'requires:repro'
-          days-before-issue-stale: 28
+          stale-issue-message: "This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 60 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment."
+          any-of-labels: 'category:new-port'
+          close-issue-label: 'info:new-port-unresolved'
+          days-before-issue-stale: 60
           days-before-pr-stale: -1
           days-before-close: 14
       - uses: actions/stale@v6
         with:
-          stale-issue-message: "This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 60 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment."
-          any-of-labels: 'category:new-port'
-          close-issue-label: 'new-port-unresolved'
-          days-before-issue-stale: 60
+          stale-issue-message: "This is an automated message. Per our repo policy, stale issues get closed if there has been no activity in the past 180 days. The issue will be automatically closed in 14 days. If you wish to keep this issue open, please add a new comment."
+          exempt-issue-labels: 'no-stale,category:new-port,category:question,requires:repro,requires:more-information'
+          days-before-issue-stale: 180
           days-before-pr-stale: -1
           days-before-close: 14

README.md

@@ -4,6 +4,7 @@
 [Español](README_es.md)
 [한국어](README_ko_KR.md)
 [Français](README_fr.md)
+[Tiếng Việt](README_vn.md)
 
 Vcpkg helps you manage C and C++ libraries on Windows, Linux and MacOS.
 This tool and ecosystem are constantly evolving, and we always appreciate contributions!
@@ -32,7 +33,7 @@ you can run `vcpkg help`, or `vcpkg help [command]` for command-specific help.
     - [Visual Studio Code with CMake Tools](#visual-studio-code-with-cmake-tools)
     - [Vcpkg with Visual Studio CMake Projects](#vcpkg-with-visual-studio-cmake-projects)
     - [Vcpkg with CLion](#vcpkg-with-clion)
-    - [Vcpkg as a Submodule](#vcpkg-as-a-submodule)
+    - [Vcpkg as a Submodule](#vcpkg-as-a-submodule-with-cmake)
 - [Tab-Completion/Auto-Completion](#tab-completionauto-completion)
 - [Examples](#examples)
 - [Contributing](#contributing)
@@ -62,11 +63,10 @@ Prerequisites:
 - [Git][getting-started:git]
 - [Visual Studio][getting-started:visual-studio] 2015 Update 3 or greater with the English language pack
 
-First, download and bootstrap vcpkg itself; it can be installed anywhere,
-but generally we recommend using vcpkg as a submodule for CMake projects,
-and installing it globally for Visual Studio projects.
-We recommend somewhere like `C:\src\vcpkg` or `C:\dev\vcpkg`,
-since otherwise you may run into path issues for some port build systems.
+First, download and bootstrap vcpkg itself; it can be installed anywhere, but generally we recommend using vcpkg as a
+submodule so the consuming repo can stay self-contained. Alternatively, vcpkg can be installed globally; we recommend
+somewhere like `C:\src\vcpkg` or `C:\dev\vcpkg`, since otherwise you may run into path issues for some port build
+systems.
 
 ```cmd
 > git clone https://github.com/microsoft/vcpkg
@@ -133,7 +133,7 @@ Prerequisites for macOS:
 - [Apple Developer Tools][getting-started:macos-dev-tools]
 
 First, download and bootstrap vcpkg itself; it can be installed anywhere,
-but generally we recommend using vcpkg as a submodule for CMake projects.
+but generally we recommend using vcpkg as a submodule.
 
 ```sh
 $ git clone https://github.com/microsoft/vcpkg
@@ -237,7 +237,7 @@ Finally, in `CMake options`, add the following line:
 
 You must add this line to each profile.
 
-### Vcpkg as a Submodule
+### Vcpkg as a Submodule with CMake
 
 When using vcpkg as a submodule of your project,
 you can add the following to your CMakeLists.txt before the first `project()` call,
@@ -321,7 +321,7 @@ places the associated license(s) in the location `installed/<triplet>/share/<por
 Most ports in vcpkg build the libraries in question using the original build system preferred
 by the original developers of those libraries, and download source code and build tools from their
 official distribution locations. For use behind a firewall, the specific access needed will depend
-on which ports are being installed. If you must install in in an "air gapped" environment, consider
+on which ports are being installed. If you must install it in an "air gapped" environment, consider
 installing once in a non-"air gapped" environment, populating an
 [asset cache](https://learn.microsoft.com/vcpkg/users/assetcaching) shared with the otherwise "air gapped" environment.
 

README_es.md

@@ -20,7 +20,7 @@ una vez instalado Vcpkg puede ejecutar `vcpkg help`, o
 * este programa en: [vcpkg-tool GitHub](https://github.com/microsoft/vcpkg-tool)
 * [Slack](https://cppalliance.org/slack/), en el canal #vcpkg
 * Discord: [\#include \<C++\>](https://www.includecpp.org), en el canal #🌏vcpkg
-* Docs: [Documentación](docs/README.md)
+* Docs: [Documentación](https://learn.microsoft.com/vcpkg)
 
 ## Tabla de contenido
 
@@ -55,7 +55,7 @@ puede [abrir una incidencia en el repositorio de GitHub][contributing:submit-iss
 donde el equipo de vcpkg y la comunidad pueden verlo, y potencialmente hacer un port a vcpkg.
 
 Después de tener Vcpkg instalado y funcionando,
-puede que desee añadir [completado con tab](#Completado-TabAuto-Completado) en su terminal.
+puede que desee añadir [completado con tab](#Completado-TabAutoCompletado) en su terminal.
 
 Finalmente, si está interesado en el futuro de Vcpkg,
 puede ver la guía de [archivos de manifiesto][getting-started:manifest-spec]!
@@ -70,11 +70,12 @@ Prerrequisitos:
 - [Git][getting-started:git]
 - [Visual Studio][getting-started:visual-studio] 2015 Update 3 o superior con el paquete Inglés de Visual Studio.
 
-Primero, descargue y compile vcpkg; puede ser instalado en cualquier lugar,
-pero generalmente recomendamos usar vcpkg como submódulo para proyectos de CMake,
-e instalándolo globalmente para Proyectos de Visual Studio.
-recomendamos un lugar como `C:\src\vcpkg` o `C:\dev\vcpkg`,
-ya que de otra forma puede encontrarse problemas de ruta para algunos sistemas de port.
+Primero, descargue y compile vcpkg; puede ser instalado en cualquier lugar, pero por lo general recomendamos usar vcpkg  
+como submódulo, asi el repositorio que lo consume puede permanecer autónomo.
+Alternativamente vcpkg puede ser instalado globalmente;
+recomendamos que sea en un lugar como `C:\src\vcpkg` o `C:\dev\vcpkg`, 
+
+ya que de otra forma puede encontrarse problemas de ruta para algunos sistemas de port. 
 
 ```cmd
 > git clone https://github.com/microsoft/vcpkg
@@ -119,9 +120,6 @@ Con CMake, todavía necesitara `find_package` y las configuraciones adicionales
 Revise la [Sección de Cmake](#usando-vcpkg-con-cmake) para más información,
 incluyendo el uso de CMake con un IDE.
 
-Para cualquier otra herramienta, incluyendo Visual Studio Code,
-reviste la [guía de integración][getting-started:integration].
-
 ### Inicio rápido: Unix
 
 Prerrequisitos para Linux:
@@ -133,8 +131,8 @@ Prerrequisitos para macOS:
 
 - [Herramientas de desarrollo de Apple][getting-started:macos-dev-tools]
 
-Primero, descargue y compile vcpkg, puede ser instalado donde sea,
-pero recomendamos usar vcpkg como submodulo para proyectos de CMake.
+Primero, descargue y compile vcpkg, puede ser instalado donde lo desee,
+pero recomendamos usar vcpkg como un submodulo.
 
 ```sh
 $ git clone https://github.com/microsoft/vcpkg
@@ -318,14 +316,13 @@ puede usar un simple `vcpkg install --feature-flags=manifests`
 
 Para más información, revise la especificación de [manifiesto][getting-started:manifest-spec]
 
-[getting-started:using-a-package]: docs/examples/installing-and-using-packages.md
-[getting-started:integration]: docs/users/buildsystems/integration.md
+[getting-started:using-a-package]: https://learn.microsoft.com/vcpkg/examples/installing-and-using-packages
 [getting-started:git]: https://git-scm.com/downloads
 [getting-started:cmake-tools]: https://marketplace.visualstudio.com/items?itemName=ms-vscode.cmake-tools
 [getting-started:linux-gcc]: #Instalando-Herramientas-de-desarrollo-en-Linux
 [getting-started:macos-dev-tools]: #Instalando-Herramientas-de-desarrollo-en-macOS
 [getting-started:visual-studio]: https://visualstudio.microsoft.com/
-[getting-started:manifest-spec]: docs/specifications/manifests.md
+[getting-started:manifest-spec]: https://learn.microsoft.com/en-us/vcpkg/users/manifests
 
 ## Completado-Tab/Autocompletado
 
@@ -347,10 +344,10 @@ según la terminal que use, luego reinicie la consola.
 
 ## Ejemplos
 
-ver la [documentación](docs/README.md) para tutoriales específicos, incluyendo
-[instalando y usando un paquete](docs/examples/installing-and-using-packages.md),
-[agregando un nuevo paquete desde un archivo comprimido](docs/examples/packaging-zipfiles.md),
-[agregando un nuevo paquete desde un repositorio en GitHub](docs/examples/packaging-github-repos.md).
+ver la [documentación](https://learn.microsoft.com/vcpkg) para tutoriales específicos, incluyendo
+[instalando y usando un paquete](https://learn.microsoft.com/vcpkg/examples/installing-and-using-packages),
+[agregando un nuevo paquete desde un archivo comprimido](https://learn.microsoft.com/vcpkg/examples/packaging-zipfiles),
+[agregando un nuevo paquete desde un repositorio en GitHub](https://learn.microsoft.com/vcpkg/examples/packaging-github-repos).
 
 Nuestra documentación también esta disponible en nuestro sitio web [vcpkg.io](https://vcpkg.io/).
 Si necesita ayuda puede [crear un incidente](https://github.com/vcpkg/vcpkg.github.io/issues).
@@ -390,7 +387,7 @@ La mayoría de los `ports` en vcpkg construyen las bibliotecas usando su sistema
 por los autores originales de las bibliotecas, y descargan el código fuente asi como las herramientas de compilación
 de sus ubicaciones de distribucion oficiales. Para aquellos que usan un firewall, el acceso dependerá de cuales `ports`
 están siendo instalados. Si tiene que instalarlos en un entorno aislado, puede instalarlos previamente en un entorno
-no aislado, generando un [caché del paquete](docs/users/assetcaching.md) compartido con el entorno aislado.
+no aislado, generando un [caché del paquete](https://learn.microsoft.com/vcpkg/users/assetcaching) compartido con el entorno aislado.
 
 ## Telemetría
 

README_fr.md

@@ -14,7 +14,7 @@ Pour une description des commandes disponibles, quand vous avez installé vcpkg,
 * GitHub: [https://github.com/microsoft/vcpkg](https://github.com/microsoft/vcpkg)
 * Slack: [https://cppalliance.org/slack/](https://cppalliance.org/slack/), the #vcpkg channel
 * Discord: [\#include \<C++\>](https://www.includecpp.org), le canal #🌏vcpkg
-* Docs: [Documentation](docs/README.md)
+* Docs: [Documentation](https://learn.microsoft.com/vcpkg)
 
 [![Build Status](https://dev.azure.com/vcpkg/public/_apis/build/status/microsoft.vcpkg.ci?branchName=master)](https://dev.azure.com/vcpkg/public/_build/latest?definitionId=29&branchName=master)
 
@@ -244,16 +244,16 @@ set(CMAKE_TOOLCHAIN_FILE "${CMAKE_CURRENT_SOURCE_DIR}/vcpkg/scripts/buildsystems
 
 Cela permettra toujours aux gens de ne pas utiliser vcpkg, en passant directement le CMAKE_TOOLCHAIN_FILE, mais cela rendra l'étape de configuration-construction légèrement plus facile.
 
-[getting-started:utiliser-un-paquet]: docs/examples/installing-and-using-packages.md
-[getting-started:integration]: docs/users/buildsystems/integration.md
+[getting-started:utiliser-un-paquet]: https://learn.microsoft.com/vcpkg/examples/installing-and-using-packages
+[getting-started:integration]: https://learn.microsoft.com/en-us/vcpkg/users/buildsystems/msbuild-integration
 [getting-started:git]: https://git-scm.com/downloads
 [getting-started:cmake-tools]: https://marketplace.visualstudio.com/items?itemName=ms-vscode.cmake-tools
 [getting-started:linux-gcc]: #installing-linux-developer-tools
 [getting-started:macos-dev-tools]: #installing-macos-developer-tools
 [getting-started:macos-brew]: #installing-gcc-on-macos
 [getting-started:macos-gcc]: #installing-gcc-on-macos
 [getting-started:visual-studio]: https://visualstudio.microsoft.com/
-[getting-started:manifest-spec]: docs/specifications/manifests.md
+[getting-started:manifest-spec]: https://learn.microsoft.com/en-us/vcpkg/users/manifests
 
 # Tab-complétion/Auto-complétion
 
@@ -274,9 +274,9 @@ selon le shell que vous utilisez, puis redémarrez la console.
 
 # Exemples
 
-Lisez la [documentation](doc/README.md) pour des instructions plus spécifiques ainsi que [l'installation et l'utilisation des paquets](docs/examples/installing-and-using-packages.md),
-[ajouter un nouveau paquet depuis un fichier zip](docs/examples/packaging-zipfiles.md),
-et [ajouter un nouveau paquet depuis un dépôt GitHub](docs/examples/packaging-github-repos.md).
+Lisez la [documentation](https://learn.microsoft.com/vcpkg) pour des instructions plus spécifiques ainsi que [l'installation et l'utilisation des paquets](https://learn.microsoft.com/vcpkg/examples/installing-and-using-packages),
+[ajouter un nouveau paquet depuis un fichier zip](https://learn.microsoft.com/vcpkg/examples/packaging-zipfiles),
+et [ajouter un nouveau paquet depuis un dépôt GitHub](https://learn.microsoft.com/vcpkg/examples/packaging-github-repos).
 
 La documentation est aussi disponible en ligne sur ReadTheDocs : <https://vcpkg.readthedocs.io/> !
 

README_ko_KR.md

@@ -17,7 +17,7 @@ Vcpkg를 설치하였다면, `vcpkg help` 명령어로 사용 가능한 명령
 * GitHub: port는 [https://github.com/microsoft/vcpkg](https://github.com/microsoft/vcpkg)에, 관련 프로그램은 [https://github.com/microsoft/vcpkg-tool](https://github.com/microsoft/vcpkg-tool)에 있습니다.
 * Slack: [https://cppalliance.org/slack/](https://cppalliance.org/slack/), #vcpkg 채널
 * Discord: [\#include \<C++\>](https://www.includecpp.org), #🌏vcpkg 채널
-* 도움말: [Documentation](docs/README.md)
+* 도움말: [Documentation](https://learn.microsoft.com/vcpkg)
 
 # 목차
 
@@ -261,16 +261,16 @@ set(CMAKE_TOOLCHAIN_FILE "${CMAKE_CURRENT_SOURCE_DIR}/vcpkg/scripts/buildsystems
 또한, 여전히 `CMAKE_TOOLCHAIN_FILE`을 직접 전달하면
 vcpkg를 사용하지 않을 수 있습니다.
 
-[getting-started:using-a-package]: docs/examples/installing-and-using-packages.md
-[getting-started:integration]: docs/users/buildsystems/integration.md
+[getting-started:using-a-package]: https://learn.microsoft.com/vcpkg/examples/installing-and-using-packages
+[getting-started:integration]: https://learn.microsoft.com/en-us/vcpkg/users/buildsystems/msbuild-integration
 [getting-started:git]: https://git-scm.com/downloads
 [getting-started:cmake-tools]: https://marketplace.visualstudio.com/items?itemName=ms-vscode.cmake-tools
 [getting-started:linux-gcc]: #installing-linux-developer-tools
 [getting-started:macos-dev-tools]: #installing-macos-developer-tools
 [getting-started:macos-brew]: #installing-gcc-on-macos
 [getting-started:macos-gcc]: #installing-gcc-on-macos
 [getting-started:visual-studio]: https://visualstudio.microsoft.com/
-[getting-started:manifest-spec]: docs/specifications/manifests.md
+[getting-started:manifest-spec]: https://learn.microsoft.com/en-us/vcpkg/users/manifests
 
 # 탭 완성/자동 완성
 
@@ -289,10 +289,10 @@ $ ./vcpkg integrate bash # or zsh
 
 # 예시
 
-[패키지 설치 및 사용](docs/examples/installing-and-using-packages.md),
-[zip 파일에서 새 패키지 추가](docs/examples/packaging-zipfiles.md),
-[GitHub 저장소에서 새 패키지 추가](docs/examples/packaging-github-repos.md)에
-대한 구체적인 예시는 [문서](docs/README.md)를 참고하세요.
+[패키지 설치 및 사용](https://learn.microsoft.com/vcpkg/examples/installing-and-using-packages),
+[zip 파일에서 새 패키지 추가](https://learn.microsoft.com/vcpkg/examples/packaging-zipfiles),
+[GitHub 저장소에서 새 패키지 추가](https://learn.microsoft.com/vcpkg/examples/packaging-github-repos)에
+대한 구체적인 예시는 [문서](https://learn.microsoft.com/vcpkg)를 참고하세요.
 
 문서는 이제 웹사이트 https://vcpkg.io/ 에서도 온라인으로 확인 가능합니다. 모든 피드백에 진심으로 감사드립니다!
 https://github.com/vcpkg/vcpkg.github.io/issues 에서 이슈를 제출할 수 있습니다.
@@ -331,7 +331,7 @@ Vcpk가 제공하는 대부분의 port는 각각의 라이브러리를 빌드할
 소스 코드와 빌드 도구를 각각의 공식 배포처로부터 다운로드합니다.
 방화벽 뒤에서 사용하는 경우, 어떤 port를 설치하느냐에 따라 필요한 접근 권한이 달라질 수 있습니다.
 만약 "air gapped" 환경에서 설치해야만 한다면, "air gapped"가 아닌 환경에서 
-[asset 캐시](docs/users/assetcaching.md)를 다운로드하고, 
+[asset 캐시](https://learn.microsoft.com/vcpkg/users/assetcaching)를 다운로드하고, 
 이후에 "air gapped" 환경에서 공유하는 것을 고려해 보십시오.
 
 # 데이터 수집