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
Per the discussion in #2921, since Casks can support multiple artifacts of different types, it would be desirable to give the user a way to control which artifacts are installed.
Currently we have a --no-binaries option. This could perhaps be generalized to --artifact-include= and --artifact-exclude=.
The use-case discussed in #2921 is: installing only symlinks to executables (binary artifact) when the App itself is already installed via the App Store. For that particular use-case, the binary artifact would also need to be extended to check multiple locations for the symlink source.
The text was updated successfully, but these errors were encountered:
Per the discussion in #2921, since Casks can support multiple artifacts of different types, it would be desirable to give the user a way to control which artifacts are installed.
Currently we have a
--no-binaries
option. This could perhaps be generalized to--artifact-include=
and--artifact-exclude=
.The use-case discussed in #2921 is: installing only symlinks to executables (
binary
artifact) when the App itself is already installed via the App Store. For that particular use-case, thebinary
artifact would also need to be extended to check multiple locations for the symlink source.The text was updated successfully, but these errors were encountered: