XPost: linux.debian.bugs.dist
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?
<div dir="ltr"><div dir="ltr"><div>I see two complaints about the "todo" virtual package:<br></div><div> 1) it encompasses applications that may not have sufficiently identical interfaces, and/or </div><div> 2) it uses Conflicts as a
transition mechanism.</div><div><br></div><div>Resolving (2) exceeds my threshold. I'll drop the todo package.</div><div><br></div><div>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:</div><div> - it properly supports the "--info" argument<br></div><div> - it supports
calling the hooks in the optional todo.txt-base package</div><div> - 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.</div><div><br></div><
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.</div><div><br></div><div>I'm trying to do this in good faith.</div>
<div><br></div><div>Any objections? Actions? Suggestion for the description?</div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)