Hi Guillaume, * Guillaume Yziquel <guillaume.yziq...@mailfence.com> [2024-05-26 09:30]:
For various development reaons on my machine, I had to install the go-task task tool. It is a task runner in the go ecosystem that has named its executable... task.https://github.com/go-task/task.git This very obviously conflicts with the name of taskwarrior's executable. Which saddens me a lot. That naming choice from go-task is most unfortunate. But I do not expect this name conflict to be of major importance to them. But I need both taskwarrior and go-task's task. Because I use go-task's task in a git repository, and use custom taskwarrior configuration to handle a local bug-tracker local to the same git repository. I would therefore appreciate, even if I do not have much hope on that front, that debian packaging and the go-task team could come up with an agreement on the name used here. As to myself, I'll be looking at a way to rename the task taskwarrior executable on my system, possibly by modifying the debian packaging.
As long as go-task is not part of Debian I don't think we should act on this. Otherwise Debian policy 10.1 has something on name conflicts:
https://www.debian.org/doc/debian-policy/ch-files.html#s-binaries
P.S.: using ubuntu (for the moment), but I believe debian is the right place to report this bug.
I would rather recommend adding symbolic links in /usr/local/bin or ~/.local/bin with the new names.
Cheers Jochen
signature.asc
Description: PGP signature
