Skip to content

fix(release): pass the service environment to the cask's install verbatim - #93

Merged
vishr merged 1 commit into
mainfrom
fix/cask-service-env
Oct 31, 2026
Merged

vishr merged 1 commit into
mainfrom
fix/cask-service-env

Conversation

@vishr

@vishr vishr commented Oct 31, 2026

Copy link
Copy Markdown
Member

The Homebrew cask's postflight re-ran driga service install with the old
plist's environment through system_command's env: option. Homebrew
shell-escapes env: values but runs no shell, so DRIGA_DATA_DIR became
"/Users/me/Library/Application\ Support/driga" with a literal backslash.
Every upgrade then installed a service collecting into a stray directory,
and the app and CLI fell back to snapshot mode.

The postflight now runs /usr/bin/env with the assignments as arguments,
which Homebrew passes unchanged. The cask test uses a data directory with a
space, and the release check requires the new form and rejects env:.

…atim

The Homebrew cask's postflight re-ran driga service install with the old
plist's environment through system_command's env: option. Homebrew
shell-escapes env: values but runs no shell, so DRIGA_DATA_DIR became
"/Users/me/Library/Application\ Support/driga" with a literal backslash.
Every upgrade then installed a service collecting into a stray directory,
and the app and CLI fell back to snapshot mode.

The postflight now runs /usr/bin/env with the assignments as arguments,
which Homebrew passes unchanged. The cask test uses a data directory with a
space, and the release check requires the new form and rejects env:.
@vishr
vishr merged commit f3083db into main Oct 31, 2026
7 checks passed
@vishr
vishr deleted the fix/cask-service-env branch October 31, 2026 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant