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
Sometimes people name programs the same. A good example of this is packer, which is a popular image building tool from Hashicorp, but also exists in RHEL as a core binary that manages parts of the keyring.
whalebrew already supports custom command name configuration via the io.whalebrew.name label, however it would be great if whalebrew checked for the existence of that command during the install, and had some sort of option to automatically switch to an alternate command name, or an option to override the system command on the user path.
Example Use Cases
Ruby
Ruby is installed on every mac, but you should basically never use it when doing any project that utilizes Ruby, gems, rails, etc...
There could be a io.whalebrew.options.override_system_binary label, or flag during install
packer
As described above, there is a conflict with packer, in that they're two totally different tools. Unlike the system conflict example for ruby, we can use any name for the packer command if the system already has packer on the system path.
There could be a io.whalebrew.alternate_name that I could set to something like packerd
The text was updated successfully, but these errors were encountered:
This isn't the highest priority feature, but it would be a definite "nice to have". It would probably rely or is related to #17.
LongLiveCHIEF
changed the title
Automatic Alternate command detection | override system command
Enhancement: Automatic Alternate command detection | override system command
Jan 28, 2017
Sometimes people name programs the same. A good example of this is
packer
, which is a popular image building tool from Hashicorp, but also exists in RHEL as a core binary that manages parts of the keyring.whalebrew already supports custom command name configuration via the
io.whalebrew.name
label, however it would be great if whalebrew checked for the existence of that command during the install, and had some sort of option to automatically switch to an alternate command name, or an option to override the system command on the user path.Example Use Cases
Ruby
Ruby is installed on every mac, but you should basically never use it when doing any project that utilizes Ruby, gems, rails, etc...
io.whalebrew.options.override_system_binary
label, or flag during installpacker
As described above, there is a conflict with
packer
, in that they're two totally different tools. Unlike the system conflict example for ruby, we can use any name for the packer command if the system already haspacker
on the system path.io.whalebrew.alternate_name
that I could set to something likepackerd
The text was updated successfully, but these errors were encountered: