-
-
Notifications
You must be signed in to change notification settings - Fork 302
look for Brewfile in HOMEBREW_USER_CONFIG_HOME #1549
Conversation
When --global is set, use `$HOMEBREW_USER_CONFIG_HOME/Brewfile` if it exists before falling back to `~/.Brewfile`.
This is the only part I'm 👎🏻 on, I don't see any users wanting this.
The current location. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code mostly makes sense so far. I'd be 👍🏻 on supporting behaviour change if XDG_CONFIG_HOME
is set and otherwise I'd like to leave everything as-is. Thanks!
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
329862a
to
37dc2d4
Compare
dba5349
to
28bf5f9
Compare
Updated help text, added spec. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @rrotter, great work!
@MikeMcQuaid, thanks. I went through several iterations on the help text before committing this. Not at all bothered that you decided to tweak it, but I just want to point out that I specifically avoided mentioning $HOMEBREW_USER_CONFIG_HOME in the help text (even though it's in the PR title) because it's a brew internal variable which can't be set by the user: https://github.com/Homebrew/brew/blob/9fd2b27a353726b2ea1641b9b0477d5cc25ac595/bin/brew#L172-L177 |
- address #1549 (comment) by referencing `XDG_CONFIG_HOME` rather than `HOMEBREW_USER_CONFIG_HOME` (and internal variable). - Use environment variable names consistently.
Indirectly support XDG_CONFIG_HOME by leaning on
brew
's support for it.when
--global
is set, we'll get the brewfile from:but if this doesn't exist either, we should probably use $HOMEBREW_USER_CONFIG_HOME/Brewfile as the new default[edit: per feedback])Starting this as a draft because:
brew bundle --help
text