Balachandran Sivakumar <[email protected]> writes:

> Hi Simon,
>
> On 21/08/26 12:00, Simon Josefsson wrote:
>> Please no.  There is no RENAME in Debian, the only package operations
>> are ADD and REMOVE.  Renaming like that will mean a lot of package
>> renaming churn, and lots of NEW reviews and ftp-master RM activity.
>>
>> How about adding 'Provides: golang-github-alecthomas-chroma-v2-dev' to
>> those packages instead?
>
>     Thanks for explaining that. Sorry about getting it wrong. I'll
> work on a tool that does this.

My opinion isn't necessarily right, so further discussion may provide
more insight.

> So, something like dh-fixdeps-golang [--show-changes] <pkg-name>

I think a team-maintained common "improve this Go package" tool would be
quite useful, extending beyond just this particular fix.

I have my own scripts that fixes nits, but the scripts aren't polished
enough to upload into Salsa or have any else run them at this point.
Maybe I should just upload what I have to start the ball...

/Simon

> where passing the --show-changes will just show the changes, but not
> do any modifications to debian/control.
>
> Also, are the following assumptions correct?
>
> 1. The `pkg-name` will be cloned from salsa's Debian Go
>
> 2. The person running the tool will have at least read access to
> salsa/go-team
>
> 3. The changes will remain local, at least initially for them to
> review, commit and push
>
>> If/when a v3 arrives, things will over time migrate to the proper
>> solution, and meanwhile we have a small non-intrusive transition
>> mechanism that ought to work.
>>
> Yes, sure. This would keep the disruptions at a minimum. Thanks
>
> --
> Thank you,
> Balachandran Sivakumar
>
>
>

Attachment: signature.asc
Description: PGP signature

Reply via email to