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

Naming conflict with taskwarrior. #1672

Closed
gl-yziquel opened this issue May 26, 2024 · 2 comments
Closed

Naming conflict with taskwarrior. #1672

gl-yziquel opened this issue May 26, 2024 · 2 comments
Labels
state: wontfix The issue will not be progressed or fixed.

Comments

@gl-yziquel
Copy link

gl-yziquel commented May 26, 2024

Hi.

I do not know what may be done or not about this, but I experience a naming conflict. go-task's task tool and taskwarrior's task tool share the same name.

I do not expect a renaming of either, but that name conflicts impacts me. I indeed use taskwarrior as a locally configured and locally set up bug tracker on my machine. Local to a git repo. I find it pretty much convenient. Until that name conflict.

I opened a bug report on Debian's Bug Tracking system.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071939

And on taskwarrior's github repos:

GothenburgBitFactory/taskwarrior#3463
GothenburgBitFactory/taskshell#75

Anyway...

Good luck with your task runner development.

Best.

@gl-yziquel
Copy link
Author

The code below allows to set TASKBIN to define the path for the taskwarrior executable in the task shell tasksh.

https://github.com/gl-yziquel/taskshell/tree/v1.2.0-yziquel

This helps circumvent the name clash between taskwarrior and go-task for the task executables.

@pd93
Copy link
Member

pd93 commented Jun 8, 2024

This has been discussed at length in the past. There is not much that we or the maintainers of taskwarrior can do about this given that both tools are well established. The number of users that have both installed is fairly small and some basic knowledge of PATH and aliases can help to avoid conflicts - much like the tool you linked.

@pd93 pd93 closed this as completed Jun 8, 2024
@pd93 pd93 added state: wontfix The issue will not be progressed or fixed. and removed state: needs triage Waiting to be triaged by a maintainer. labels Jun 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state: wontfix The issue will not be progressed or fixed.
Projects
None yet
Development

No branches or pull requests

3 participants