/usr/bin/helm conflict with Kubernetes helm

[fpesari]

Hello,

there are two helms around: the amazing synth, and a Kubernetes package manager.

This creates a conflict in distro package managers, which has been solved by some packagers only in terms of package names (e.g. helm and helm-synth or helm and kubernetes-helm), not binaries - so, installing one of the two helms overwrites the other.

I think that it's unlikely that both are installed on the same machine, since they belong to two completely different fields, however it would be nice to make life easier for distro maintainers if they did not conflict.

Since it's much harder to ask a Foundation ran by huge corporations (Google, CoreOS, Mesosphere, Red Hat, Twitter, Huawei, Intel, Cisco, IBM, Docker, Univa, and VMware, according to Wikipedia) and a huge userbase to rename their binaries, maybe this helm could have an executable called /usr/bin/helm-synth instead of /usr/bin/helm, to make life easier for packagers.

Otherwise packagers should do it themselves, but they might not be aware that another helm exists so they should all be contacted individually.

[falkTX]

Renaming the binary to Helm is enough to get around this

[mtytel]

Yeah I just might go capitals. I believe Google took the name after I did, but I still get the brunt of the blame.

[fpesari]

Yeah I just might go capitals. I believe Google took the name after I did, but I still get the brunt of the blame.

I did not blame you, I just said that you might be reasonable about such a request, Google, well, probably not :smile:

[tsanecki]

I am a software developer and a hobbyist musician as well. I was surprised when my application build scripts have suddenly opened helm synth.