Hi. >When I packaged the prometheus ecosystem, most of the vendored >dependencies were not present in Debian. I packaged about 30 different >libraries to remove vendoring and left just a couple of them. There >were a couple of libs that were just too small and specific to justify >separate packages (not used directly by prometheus), and in the case of >the consul API because there is an API incompatibility with the package >present in Debian.
I get the point. I tried to review that vendored library's compability with already debian packaged libraries. Does it make sense? === hashicorp/go-cleanhttp Compability: OK, almost same(only comment change: https://github.com/hashicorp/go-cleanhttp/commit/ad28ea4487f05916463e2423a55166280e8254b5), used from only consul (not prometheus) === hashicorp/consul Compability: Some codes are older than golang-github-hashicorp-consul-dev package === hashicorp/serf Compability: Looks good, Almost same(unnecessary codes were removed and a short comment is different: https://github.com/hashicorp/serf/commit/979180d19cb3c60f58fda490533e8e22a21c5aae) === influxdb/influxdb Compability: Complex, looks hard to replace with golang-github-influxdb-influxdb-dev package, there are incompatible changes. === > But I disagree with the severity of this bug, the policy only marks >this requirement as a "should", so it is not serious. OK. Thanks. -- Haruki TSURUMOTO PGP Fingerprint:3718 C84E 4EDA 1B5C 4F26 8639 9D3D EE3F 63A6 000E
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
