You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current iteration of pkg_install was only tested on Linux and macOS. I currently do not have a Windows development environment available, so things were likely to be missed.
Unfortunately windows package install does not work on Windows as far as I could test, with an error like:
Traceback (most recent call last):
File "C:\Users\redsun82\AppData\Local\Temp\Bazel.runfiles_wd_pz4_y\runfiles\_main\go\_extractor-pack-installer_install_script.py", line 203, in <module>
exit(main(sys.argv))
^^^^^^^^^^^^^^
File "C:\Users\redsun82\AppData\Local\Temp\Bazel.runfiles_wd_pz4_y\runfiles\_main\go\_extractor-pack-installer_install_script.py", line 195, in main
installer.include_manifest_path(f)
File "C:\Users\redsun82\AppData\Local\Temp\Bazel.runfiles_wd_pz4_y\runfiles\_main\go\_extractor-pack-installer_install_script.py", line 123, in include_manifest_path
with open(path, 'r') as fh:
^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: 'go/_extractor-pack-installer_install_script-install-manifest.json'
I might be able to do some debugging and maybe come up with a patch for this in the coming days.
Perhaps, we can use commands related to Wix3 and NSIS to allow users to create Wix or NSI script files, and Bazel can use these script files for packaging. As for zip, we might use PowerShell's Compress-Archive?
I think there is already an issue to make a pkg_msi or equivalent. But there is little chance any of the maintainers are going to work on that.
That aside, it is a different feature set than what pkg_install does.
Activity
redsun82 commentedon Apr 29, 2024
Unfortunately windows package install does not work on Windows as far as I could test, with an error like:
I might be able to do some debugging and maybe come up with a patch for this in the coming days.
hsjdhudn commentedon Oct 12, 2025
Perhaps, we can use commands related to Wix3 and NSIS to allow users to create Wix or NSI script files, and Bazel can use these script files for packaging. As for zip, we might use PowerShell's Compress-Archive?
tonyaiuto commentedon Oct 14, 2025
I think there is already an issue to make a pkg_msi or equivalent. But there is little chance any of the maintainers are going to work on that.
That aside, it is a different feature set than what pkg_install does.
rdesgroppes commentedon Nov 5, 2025
On Windows, "runfiles" aren't enabled by default, which can be changed by executing
bazel run --enable_runfiles.RUNFILES_DIRenv var is set,RUNFILES_MANIFEST_FILEenv var is set instead.This is hopefully addressed by:
pkg_installwork without "runfiles" (Windows default) #984.Make `pkg_install` work without runfiles (Windows default)
Make `pkg_install` work without runfiles (Windows default)
Make `pkg_install` work without runfiles (Windows default)
Make `pkg_install` work without runfiles (Windows default)
Make `pkg_install` work without "runfiles" (Windows default) (#984)
Make `pkg_install` work without runfiles (Windows default)