Source: libpinyin Version: 2.6.0-1 Severity: normal Tags: sid bookworm X-Debbugs-CC: czchen@debian.org alexepico@gmail.com Dear Debian Input Method team members, Currently libpinyin in Debian is using Berkeley DB (libdb-dev). After the release of Debian 11, Debian has a release goal proposal to remove Berkeley DB due to its problematic AGPLv3 license issue (for details, see https://bugs.debian.org/987013 ). It seems that libpinyin also supports Keyto Cabinet as DBM. I believe we should consider switching to it to avoid dependency on Berkeley DB. It may also solve some old problems such as https://tests.reproducible-builds.org/debian/issues/unstable/berkeley_db_variation_requiring_further_investigation_issue.html and https://tests.reproducible-builds.org/debian/issues/unstable/randomness_in_files_generated_by_pinyin_gen_binary_files_issue.html . However, I am not sure what would users experience when database format is switched (e.g., will all data previously stored in old db be lost? Is that a severe issue?). Even with such side effect, I believe the benefit would be more significant and we should perform the switch within current development cycle. P.S. I am also aware of https://github.com/libpinyin/libpinyin/issues/140 , and tkrzw is being reviewed by Debian FTP Masters at https://ftp-master.debian.org/new/tkrzw_1.0.0+dfsg1-1.html . -- Thanks, Boyuan Yang
Attachment:
signature.asc
Description: This is a digitally signed message part