Balachandran Sivakumar <[email protected]> writes: > Hi all, > > I am starting work on the next item for dh-make-golang in the > DebConf '26 list - "Mass Refactoring Script for Reverse > Dependencies"[1] > > I have a few questions around this so that I understand this better. > > 1. Suppose there already exists a package named > golang-github-alecthomas-chroma. And the go module is actually > github.com/alecthomas/chroma/v2. How do we handle this? Would it be > rename the current one as golang-github-alecthomas-chroma-v2 and then > a package for golang-github-alecthomas-chroma as a transitional > package with "Depends" on golang-github-alecthomas-chroma-v2?
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? 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. /Simon
signature.asc
Description: PGP signature
