On 2022-06-01 16:30:55, Anthony Fok wrote:
> Control: reopen -1
> Control: severity -1 important
>
> Hi Antoine!
>
> Thank you for your quick response!
>
> On Tue, May 31, 2022 at 9:58 AM Antoine Beaupré <anar...@debian.org> wrote:

[...]

>> This seems like it's the opposite of what I was suggesting in the bug
>> report (#1011545). And you even refer to that bug report in the
>> changelog:
>>
>>     * Limit "Conflicts: gitsome" to older (<< 0.8.0+ds-7.1) versions.
>>       Thanks to Antoine Beaupre for the suggestion, and for resolving the
>>       file conflict with gitsome (#1005858) so amicably! (Closes: #1011545)
>>
>> What actually happened, from what I can tell, is that you just removed
>> the Conflicts... I don't think that's the right resolution here: gitsome
>> has been fixed, in unstable, and gh doesn't need to go around with fancy
>> diversion stuff, because we're *precisely* not in a situation like
>> moreutils and parallel...
>
> Thank you for clarifying to me that it is a different situation than
> moreutils and parallel.
>
> From my understanding of the gitsome, the "gitsome" command itself is
> mostly just a wrapper that calls xonsh, and gitsome's main
> functionalities are actually in the "/usr/bin/gh" Python executable,
> so perhaps removing /usr/bin/gh altogether in some sense cripples the
> gitsome package, and a rename to /usr/bin/gh.gitsome or something else
> would be more appropriate.

I see, I hadn't realized that. I thought gh was kind of a vanity shim,
not a different functionality.

[...]

>> Could this change be reverted?
>
> Yes, most definitely!  I will do it ASAP.

Thanks!

> After that, I will probably try to work on the gitsome package too and
> install its gh as /usr/bin/gh.gitsome and hopefully get its
> command-line completion to work with the name change, but that's
> unrelated to this particular bug report and to GitHub CLI gh.  Let's
> keep this package clean and free of the fancy and confusing diversion
> stuff.  :-)

I am not sure you should get invested deeply into gitsome. Upstream
seems inactive and you'd be basically working on your own fork...

> Thanks again for writing to me and put some common sense back into me!

Bah... "common sense", it's super complicated, and there's no easy
solution for stuff like this...

a.

-- 
We will create a civilization of the Mind in Cyberspace. May it be
more humane and fair than the world your governments have made
before.
                         - John Perry Barlow

Reply via email to