Homebrew is a cask surface here, not homebrew/core. The cask installs the BrowserBox binary and then downloads release.manifest.json and .sig into:
~/.config/dosaygo/bbpro/
Both files are checksum-verified during install.
It does not try to run privileged machine setup inside the cask transaction.
Chocolatey supports package parameters. The scaffold accepts:
/Hostname:<value>/Email:<value>
When both are present, the installer runs:
browserbox.exe --full-install <hostname> <email>Otherwise it installs the binary and prints the next-step command.
It also downloads release.manifest.json and .sig into %ProgramData%\dosaygo\bbpro\ with a user-config fallback when global writes are unavailable.
The Linux packages install the standalone binary and use a conservative postinstall script:
- the package ships
release.manifest.jsonand.sig - the installed wrapper exports
BBX_RELEASE_MANIFEST_PATH=/usr/share/dosaygo/bbpro/release.manifest.json - if
BROWSERBOX_HOSTNAMEandBROWSERBOX_EMAILare set, it runsbrowserbox --full-install - otherwise it prints the exact follow-up command
This avoids turning apt and dnf transactions into implicit interactive provisioning.
The Nix surface packages the public Linux binary as unfree, redistributable software.
It packages the binary plus release.manifest.json and .sig, then wraps browserbox with BBX_RELEASE_MANIFEST_PATH pointing into the store.
Operators still run:
browserbox --full-install <hostname> <email>