[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#976402: marked as done (Proposed official virtual packages - todo and todo.txt)

Your message dated Thu, 27 Jan 2022 15:11:51 -0700
with message-id <87wnik96c8.fsf@melete.silentflame.com>
and subject line Re: Bug#976402: Proposed official virtual packages - todo and todo.txt
has caused the Debian Bug report #976402,
regarding Proposed official virtual packages - todo and todo.txt
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
976402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976402
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debian-policy
Severity: wishlist
X-Debbugs-Cc: debian-devel@lists.debian.org, charlesmelara@outlook.com,
              onovy@debian.org
thanks


I'd like to propose adding the virtual packages "todo" and "todo.txt" to
the authoritative list of virtual package names. I'm submitting this per
Policy section 3.6 and the preamble to the [authoritative list].

[Todo.txt] describes an ecosystem of task management tools that revolve
around a standard for a freeform-text tasking file.

The reference cli has been packaged for some time, as "todotxt-cli". It
provides the executable "todo-txt".

An alternative cli provider, "topydo", has been recently added, adding
an executable by the same name.

I propose uniting this packages using the name "todo" - the common name
for the utility. Since not all todo list packages that may want to share
that name conform to the todo.txt standards, I also propose "todo.txt",
a strict subset of "todo", for packages which conform.

Note that topydo already implements these virtual packages, and that
there now exists a todo.txt-base packages that extends cli todo.txt
capabilities. There is also a todo.txt-cli package in Sid. This is
redundant, and has a pending RM request.

I did a screen scrape of p.d.o to find any possible collisions for these
names. There is a single package, devtodo (popcon 74, recently ITA'd),
that installs a "todo" executable. Currently, topydo Conflicts with this
package. I'd propose adding it to the "todo" virtual package.

This is a request for comment per the procedure in the list.

Please copy replies to this bug report.


[authoritative list]:
https://www.debian.org/doc/packaging-manuals/virtual-package-names-list.yaml
[Todo.txt]: http://todotxt.org/

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Hello David,

On Wed 16 Dec 2020 at 03:10PM -05, David Steele wrote:

> On Wed, Dec 16, 2020 at 2:34 PM David Steele <steele@debian.org> wrote:
>
>>
>>
>> On Wed, Dec 16, 2020 at 2:14 PM Sean Whitton <spwhitton@spwhitton.name>
>> wrote:
>>
>>>
>>> Okay, and you expect every implementation of todo.txt to have
>>> tdtcleanup?  I think we probably want to specify that as one of the (or
>>> the only?)  requirements of the virtual package.
>>>
>>
>> No, no.
>>
>> The gtd stuff is an optional add-on to todo.txt. The requirements on
>> todo.txt to support these types of add-ons I listed earlier in the thread.
>>
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976402#98

Reviewing this bug, it is still not clear to me that a virtual package
is wanted as opposed to just making /usr/bin/todo a path managed by the
alternatives system.

I'm closing the bug, but if development that has taken place in the
todo.txt world since our previous dicsussion has changed matters such
that there are concrete usecases for the virtual packages that you can
explain, then please consider opening a new bug with that explanation.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: