[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#964927: ibus-avro: Remove deps on ibus IM module packages



Thanks for your report!

On 2020-07-12 19:01, Changwoo Ryu wrote:
ibus-avro depends on ibus-gtk, ibus-gtk3 and ibus-clutter.

These IM module package are for supporting UIs and they should not be
in Depends of ibus language engine packages.

I packaged ibus-avro last year, and took those dependencies from some pre-Debian .deb package out there.

But as regards ibus-gtk and ibus-gtk3 I gave it some consideration. At that time the recommends in the ibus package with respect to those packages was a bit vague. It could lead to issues in e.g. Kubuntu. Some user installed ibus-avro which pulled ibus, but since Kubuntu is KDE based, libqt5gui5 was already there, so ibus-gtk and ibus-gtk3 were not pulled and it "didn't work".

So why Depends and not just Recommends? Well, one of the Ubuntu flavors (Lubuntu) was at least previously very focused on disk space, so by default they didn't pull Recommends. Before dropping those ibus-gtk{,3} dependencies I'd like to know how they do it today.

I see that ibus now clearly recommends ibus-gtk and ibus-gtk3, so if Lubuntu does it otherwise nowadays, those dependencies could probably be dropped from ibus-avro.

Otherwise: Do the ibus-gtk/ibus-gtk3 depends have any adverse effects?

Especially it's strange to pull ibus-clutter when no application
package in Debian uses clutter-imcontext.

TBH I know nothing about clutter, but assumed that it may be needed in some situations. If not, why would im-config set the
CLUTTER_IM_MODULE env var?

--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj


Reply to: