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?
2. To avoid build breakage, would an order like below make sense? Or
would we have to do something else?
1. Work on packages in salsa that depend only on stdlib first
2. Then work on packages that depend on (1) above
3. And then progressively the rest
3. Do I create a separate repo somewhere for dh-golang-fix-deps - if
yes, would that be in GitHub, or would it have to be in salsa.debian.org?
[1] https://wiki.debian.org/DebConf/26/Sprints/DebianGoTeam#dh-make-golang
--
Thank you,
Balachandran Sivakumar
