-
Notifications
You must be signed in to change notification settings - Fork 37
Conversation
This seems reasonable and can still be overridden in facts.d/example.yaml if it doesn't suit. |
released via 0.0.8 |
This breaks things for me when bumping up the version (with latest boxen):
|
With the following combination from the
|
This is because the following in manifests/init.pp also evaluates to /usr/local:
We could potentially do away with this declaration since this file explicitly requires homebrew however this would then fail for users who specify a different brewcask_root. Something else that could be done is to wrap the above in the following but I'm not sure how good a practice this is considered.:
|
alternatively wrap either/both in :
|
I do that pattern reguarly for sub items, the only real risk is if other declarations make more explicit options, that may or may not be what you want. For this case, as its just ensuring a directory in both base |
I think we need to support the combination of the following:
One approach we could try is check if homebrew lives at I'd like to avoid |
Thanks for staying in the loop for this one @tommeier - I appreciate it! |
Inline with #47 and Homebrew/homebrew-cask#21901 the default brewcask_root location should be changed so boxen doesn't throw warnings.