Arch Linux User Repository

Hi @ericfont, thanks for the suggestions. I just updated the package so that the vcpkg root is at /opt/vcpkg and both /opt/vcpkg and /var/cache/vcpkg are configured to be owned by the group vcpkg (with GID 499). The fixed-GID method seems to be the best we can get under this particular scenario. [ref: https://bbs.archlinux.org/viewtopic.php?id=241480] But I do also think that using vcpkg without a package manager makes more sense if the host machine is shared with other users.

Hi @carlosal1015, thanks for letting me know! The commit yesterday removed the docs/ folder. I've updated the PKGBUILD and it should work now.

@kyechou, seems, it was self fixed: today package was rebuilded as vcpkg-git-2022.03.10.r34.g6b6f5a82de-1. Sounds like temporartry git/filesystem/kernel issue.

Hi @hatred, I am unable to reproduce what you described. The commands are working fine. Perhaps you could check the branch and commit that the you're on while building the package, and what's the output of git describe --long --tags?

PKGBUILD version is '2022.02.02.r64.g8dbd66f5a7-1' but after build it is '2021.06.31.r50.gbd602277bf-1'. Clean build was tried. Also, git tags shows me all tags, including 2022.02.02, but version generation commands returns value above.

Thanks @RIscRIpt, I have updated it.

There's a warning during installation (source):

Warning: -useSystemBinaries no longer has any effect; ignored. Note that the VCPKG_USE_SYSTEM_BINARIES environment variable behavior is not changed.

Please, update PKGBUILD.

Hi @ericfont, thanks for the suggestions. I just updated the package so that the vcpkg root is at /opt/vcpkg and both /opt/vcpkg and /var/cache/vcpkg are configured to be owned by the group vcpkg (with GID 499). The fixed-GID method seems to be the best we can get under this particular scenario. [ref: https://bbs.archlinux.org/viewtopic.php?id=241480] But I do also think that using vcpkg without a package manager makes more sense if the host machine is shared with other users.

Unfortunately installing this package as root made it problematic for me to run vcpkg's example manifest tutorial (https://github.com/microsoft/vcpkg/blob/master/docs/users/manifests.md) as a regular user (https://github.com/ericfont/fibo-vcpkg-example/issues/1), which led me to use sudo priviliges when running the cmake command, which is not good practice. I brought this up in vcpkg help desk (https://github.com/microsoft/vcpkg/discussions/20541) but a couple vcpkg contributors/maintainers said:

"I don't think it is a good idea to run sudo vcpkg at all, unless you are on a throw-away system."

"It is discouraged to install vcpkg via a package manager. Use git clone to install it, then you also don't have this problem."

I also suggested I wonder if it maybe makes sense to have the /usr/share/vcpkg folder be under a new group ("vcpkg" maybe) permission rather than under sudo permissions, that way regular users could install vcpkg packages without escalating to sudo privileges. Or maybe it is best to not have an AUR package for vcpkg as that second contributor said.

Hi @poldi1405, thanks! I've added some missing dependencies based on inspecting their scripts. Please let me know if there's any other issue.