Hi all, 在 2021-11-17星期三的 00:11 +0100，Gunnar Hjalmarsson写道： > Package: src:im-config > Version: 0.49-1 > > Hello! > > Due to the im-config.desktop file, im-config is visible in software > catalogs such as Software (GNOME) and Discover (KDE). I would like to > raise the question whether it should be. > > Ideally you should have a metainfo file if you want a piece of software > handled properly by AppStream. Since im-config does not install such a > file, AppStream uses the info in the .desktop file and the control file > for now. But that behavior is deprecated, and it does so while complaining: > > https://appstream.debian.org/sid/main/issues/im-config.html > > Previously ibus was recognized by AppStream via the > org.freedesktop.IBus.Setup.desktop file. But I noticed weird user > reviews, such as users complaining about the lack of a "launch button" > to start ibus. So I proposed to hide ibus from AppStream, and upstream > approved my proposal without discussion. > > https://github.com/ibus/ibus/commit/72ca5c93 > > I think im-config is similar to ibus in this respect. It gets silently > installed when appropriate and serves in the background. It's not an > "app" for users to install and launch. > > My suggestion is that "X-AppStream-Ignore=true" is added to > im-config.desktop. An alternative would be to carefully consider how to > present im-config properly in Software and Discover, and create a > metainfo file accordingly. > > I'd better mention that e.g. fcitx5 installs a metainfo file: > > https://salsa.debian.org/input-method-team/fcitx5/-/blob/master/data/org.fcitx.Fcitx5.metainfo.xml.in > > Don't know how they thought (if they thought...). Maybe they simply see > it as an opportunity to advertise. According to my impression with fcitx5 developer, I believe the most likely reason is that fcitx5 upstream tries to push fcitx5 into Flatpak-related repos (such as Flathub [1]), and that Flathub enforces some strict restriction on AppStream/.desktop file/metainfo checking, such as reverse domain naming, etc. [1] https://fcitx-im.org/wiki/Install_Fcitx_5 > I think that the actual IM engines, OTOH, are good fits in the software > catalogs. A user may want to know "how can I input Japanese or Korean", > and it makes sense that software such as Anthy and Hangul can be found > that way. It's the value of showing the frameworks and the configuration > tool I question. IM frameworks might still be different from im-config, but eventually it's up to the developer's choice. Personally I support the idea of setting "X- AppStream-Ignore=true" for im-config.desktop shipped with Debian. -- Thanks, Boyuan Yang
Attachment:
signature.asc
Description: This is a digitally signed message part