Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: Automatic Alternate command detection | override system command #20

Open
LongLiveCHIEF opened this issue Jan 28, 2017 · 1 comment

Comments

@LongLiveCHIEF
Copy link

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
@LongLiveCHIEF
Copy link
Author

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 LongLiveCHIEF changed the title Automatic Alternate command detection | override system command Enhancement: Automatic Alternate command detection | override system command Jan 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants