Andrew Lee <[email protected]> writes: > I update the MigrationFAQ page and added `CRITICAL: Always Align > XS-Go-Import-Path with go.mod`. > https://wiki.debian.org/Teams/DebianGoTeam/MigrationFAQ
Thanks! I didn't understand this. Can we get a lintian check for this added ASAP? One thing I still don't understand: XS-Go-Import-Path should only be identical to the TOP-LEVEL go.mod module path, right? If a project has a foo/bar/baz/go.mod, then that module path should not be put into XS-Go-Import-Path, right? When it is appropriate to have multiple paths in XS-Go-Import-Path? That's used sometimes. Can we use this to add both the previous and new value? What if a project does not have a top-level go.mod but several go.mod in sub-directories? Maybe this is not common. Maybe synthesize a XS-Go-Import-Path with a value above the go.mod module paths in sub-directories? If I ever find a project like that, I'll bring it up. /Simon
signature.asc
Description: PGP signature
