[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Using debian/vendor/ in Go packages?





Le jeu. 3 avr. 2025 à 10:30, Simon Josefsson <simon@josefsson.org> a écrit :
Jérémy Lal <kapouer@melix.org> writes:
> When there are dependencies that won't ever change for some reason, and
> that are useless to other packages,
> you can copy them in debian/vendor/ (this typically happens with test
> dependencies using a deprecated module).
>
> For dependencies that may be updated, but don't make sense to be packaged
> in Debian (not stable enough, or
> used by almost no other modules), it makes more sense to make a
> multiple-upstream-tarball using "component" in watch file,
> see uscan(1) and
> https://codesearch.debian.net/search?q=component%3Dgolang+path%3Adebian%2Fwatch

Do we have a good recipe on how to do that?  The receptor watch file
helps, but I'm not sure how to adapt the debian/rules...

Nothing related to that in d/rules.
 
Packaging 'ssh-tpm-agent' is stalled on determining how to deal with two
build dependencies that are questionable as standalone Debian packages:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1082814

If there is some nice simple way to add them as components and build the
resulting package easily, that would help here.

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 => ./golang-github-prep-socketpair
+replace github.com/jupp0r/go-priority-queue => ./golang-github-jupp0r-go-priority-queue

Does dh-golang allow that configuration without the need for a patch ?

Reply to: