3 ms·
Hmm. We were able to get the pip handle so didn't see major conflicts in our target space. Are there places in code/cli where we could name conflict with the pa
by akarve 9y ago
Hmm. We were able to get the pip handle so didn't see major conflicts in our target space. Are there places in code/cli where we could name conflict with the patch sets manager?
- xyzzy_plugh 9y agoI think it conflicts a bit: $ brew install quilt >/dev/null 2>&1 && which quilt /usr/local/bin/quilt I have used it extensively in automation in the past. I don't know if it's a good idea to call it "quilt" on the $PATH. Maybe "dataquilt" or "data-quilt"? "quilted"?
- raimue 9y agoWhen choosing a name, you should check the package manager index sites of large distros for potential conflicts. For example in Debian: https://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=contents&keywords=quilt https://packages.debian.org/search?suite=default§ion=all...
- masklinn 9y agoQuilt is a patchset manager and used a lot in linux distro spaces (it was created by one of Linux's maintainers for his own use). Any global install of your tool will conflict with its existence since the utility names are the same, which you'll get will depend on your PATH setup.