I would take the lack of response to indicate that nobody has any strong objections to packaging the .bdic files inside the existing Hunspell binary packages. This means that there is a consensus on the following two items: 1. The .bdic files should be compiled at package creation time instead of at package install time. 2. The .bdic files should be shipped in the existing Hunspell language binary packages. The next question that needs to be decided is where these files should be placed. There have been a number of locations proposed. I think the majority of the options are that they should not be placed in /usr/share/hunspell. Of all the proposals that have been suggested, I personally like /usr/share/ hunspell-bdic because this location is usage agnostic. Chromium can start using them in the future, Qt WebEngine can use them now, and other programs we haven't considered can use them in the future all without a need to change the name of the file location and without the name feeling like it is limited to certain programs. This would also require the the Debain Qt/KDE Maintainers add a symlink from / usr/share/qt5/qtwebengine_dictionaries and /usr/share/qt6/ qtwebengine_dictionaries to /usr/share/hunspell-bdic. They can do this in whatever package makes the most sense to them, but possibly in libqt5webengine-data and libqt6webengine6-data. Is there anyone who objects to this file location and symlink approach? On Thursday, November 3, 2022 3:31:20 PM MST Soren Stoutner wrote: > The next question that needs to be answered is if we should create new > binary packages for the .bdic files or if we should ship them as part of > the existing Hunspell language binary packages. The opinions that have > been expressed so far have run the gamut on both sides, but my sense is > they lean a little towards shipping them in the existing Hunspell packages > so as to not add 80+ new packages to Debian that only contain a few files > each. > > Is there anyone who feels strongly that they should not be shipped in the > existing files? -- Soren Stoutner soren@stoutner.com
Attachment:
signature.asc
Description: This is a digitally signed message part.