I see two complaints about the "todo" virtual package:
1) it encompasses applications that may not have sufficiently identical interfaces, and/or
2) it uses Conflicts as a transition mechanism.
Resolving (2) exceeds my threshold. I'll drop the todo package.
That leaves todo.txt, implemented by topydo and (hopefully, soon) todotxt-cli. Unfortunately, (1) has been invoked here as well - the command sets of the two packages are close, but not identical. Also, I'm on record saying an emacs script could comply if:
- it properly supports the "--info" argument
- it supports calling the hooks in the optional todo.txt-base package
- it provides a means to add/modify/delete/show tasks housed in a todo.txt-format file, noting that the format does not have to be strictly enforced by the package.
My latest stake in the ground - I claim that the functionality of the todo.txt virtual package, from a Policy perspective, is defined, here, and that the candidates are compliant.
I'm trying to do this in good faith.
Any objections? Actions? Suggestion for the description?