On Mon, Dec 26 2022 at 10:32:20 AM -0700, Soren Stoutner
<so...@stoutner.com> wrote:
Dmitry
It hasnāt been discussed, but I think it would make sense for
Chromium to ship the convert_dict tool as it is the upstream for the
project. I suppose the reason why the discussion was around how it
is shipped in the Qt packages was because that is the only place it
is currently shipped in Debian:
<https://packages.debian.org/search?searchon=contents&keywords=convert_dict&mode=path&suite=testing&arch=any>
Andres, do you have an comments on the feasibility of shipping
convert_dict as part of a Chromium package targeted at developers?
It's definitely feasible*. However, there's the question of whether we
want other important packages depending on chromium.
https://bugs.debian.org/1004441 shows that it's still an outstanding
question whether chromium will even ship in bookworm. I now have Tim
helping with packaging, which is wonderful and a huge help (thanks
Tim!), but he doesn't have upload privs. If I were to get hit by a bus
(or more likely, hit by š±Responsibilitiesš±), he'd have to find
someone else to sponsor his upload. Without his help, I'm not sure I'd
want commit to the next 3 years of security support. So the question of
other packages build-depending on convert_dict from chromium will
involve the release team and what we decide to do for bookworm.
* for my own future reference: ninja -j$(njobs) -C out/Release
convert_dict; install ./out/Release/convert_dict
--
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-talk
