Re: Using debian/vendor/ in Go packages?

[Jérémy Lal <kapouer@melix.org>]

Actua

Le jeu. 3 avr. 2025 à 11:49, Jérémy Lal <kapouer@melix.org> a écrit :

Le jeu. 3 avr. 2025 à 11:44, Pirate Praveen <praveen@onenetbeyond.org> a écrit :

On 4/3/25 2:07 PM, Jérémy Lal wrote:
> It's as simple as declaring in d/watch and d/copyright and then uscan/
> gbp import-orig.
> Lacking a nicer way, I patched go.mod to append:
>
> +replace github.com/prep/socketpair <http://github.com/prep/socketpair>
> => ./golang-github-prep-socketpair
> +replace github.com/jupp0r/go-priority-queue <http://github.com/jupp0r/
> go-priority-queue> => ./golang-github-jupp0r-go-priority-queue
>
> Does dh-golang allow that configuration without the need for a patch ?

You can create them as vendor in package directory. See
https://salsa.debian.org/ruby-team/gitlab/-/blob/master/debian/rules?ref_type=heads#L22

I don't use uscan/watch, but manually maintain a single vendor tarball.
If you want to use uscan/watch - you will need to recreate the vendor
directory structure. May be patching go.mod is simpler?

Actually there is no need to patch go.mod !

One just has to move each M.U.T. component to the right _build directory:

execute_before_dh_auto_build:
  mkdir -p _build/src/github.com/prep
  ln -srf golang-github-prep-socketpair _build/src/github.com/prep/socketpair
  mkdir -p _build/src/github.com/jupp0r
  ln -srf golang-github-jupp0r-go-priority-queue _build/src/github.com/jupp0r/go-priority-queue

In theory, the right path being recorded in go.mod, the line above could be simplified.

Something with "go list ..." ?

Any idea ?