Le dim. 3 août 2025 à 20:47, Leonardo Arias Fonseca <
agami@riseup.net> a écrit :
On 8/3/25 11:49 AM, Otto Kekäläinen wrote:
> We can
> do our part in Debian by educating our upstreams and filing requests
> upstream to cut down on the number of excessive dependencies.
Is there good guidance about when to add a dependency, when to copy the
code, and when to reimplement it from scratch?
There is a fourth alternative: Multiple Upstream Tarballs.
I will try to add a ctype=golang to uscan so that it works as nicely as possible.
While navigating the neverending list of dependencies for packaging
mev-boost [1], I filed a few bugs like:
depends on unmaintained go-accept-headers
https://github.com/flashbots/mev-boost/issues/807
I know these are bugs, and not just suggestions. I might lack the
authority to support this claim :)
[1] Intent to package bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107167