Hi,

Unvendoring libraries that are already in Debian seems like the pragmatic approach to lower code duplication and be closer to better packaging pratices.

#1073005 asks for the vendoring back of an unvendored library, arguing
that this particular library is unmaintained upstream, implying that the vendored fork is better maintained.

My view on this is that if the vendored fork is better maintained, the
vendored fork should become the upstream of the Debian package.

I've read through https://bugs.debian.org/907051 (policy bug: Say much more about vendoring of libraries) and do feel I understand the rules and the philosophy behind those rules.

On the other side I do not want to make it harder for downstream distributions packagers to do their work for no good reason.

Seeking additional advice here.

Thanks,

Alex

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Enriching original email:

This is about whether packages transmission-gtk should use embedded copy of libb64 or depend on the outdated Debian package libb64.

Upstream for libb64 seems dead and transmission devs have improved their embedded/vendored copy of libb64.

Direct link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073005


First question: Are the libb64 improvements by Transmission devs generic,
could they be copied as patches to the Debian libb64 package for everyone's benefit?

<div dir="auto">Enriching original email:<div dir="auto"><br></div><div dir="auto">This is about whether packages transmission-gtk should use embedded copy of libb64 or depend on the outdated Debian package libb64.</div><div dir="auto"><br></div><div dir=
"auto">Upstream for libb64 seems dead and transmission devs have improved their embedded/vendored copy of libb64.<br><div dir="auto"><br></div><div dir="auto">Direct link: <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073005">https://bugs.
debian.org/cgi-bin/bugreport.cgi?bug=1073005</a></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">First question: Are the libb64 improvements by Transmission devs generic, could they be copied as patches to the Debian libb64
package for everyone&#39;s benefit?</div><div dir="auto"><br></div></div></div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

I implemented base64 decoding a long time ago.

It's a few lines of C code. It's very simple really. What maintainance does
the upstream library need? Keeping in mind that base64 encoding hasn't changed since it has been invented?

I am perplexed about the need to bundle this specific library, I could understand if it was something more complicated.

--
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

https://ltworf.codeberg.page/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)