Re: Replacing Fcitx4 with Fcitx5 in Factory

On Mon, 27 Dec 2021 10:16:39 +0100,
Takashi Iwai wrote:
> 
> On Sun, 19 Dec 2021 03:25:40 +0100,
> Fusion Future wrote:
> > 
> > On 2021/12/19 01:24, Nianqing Yao wrote:
> > > Hi everyone,
> > >
> > > There's a input method framework called fcitx4 shipped with openSUSE Tumbleweed and Leap, but when the whole project turns to new fcitx5, fcitx4 seems to be abounded and outdated. As far as I know, fcitx5 only exists in i18n project on the OBS, not in the main OSS repo. Could it possible to replace fcitx4 with fcitx5 in factory's OSS repo? So that Tumbleweed and Leap will finally benefit from it.
> > 
> > I agree with you. Fcitx 4 is outdated and openSUSE already has Fcitx 5
> > in M17N repo. Fcitx 5 is much more usable on Wayland and is mature
> > enough for daily use. It should be pushed to Factory as soon as
> > possible.
> 
> I believe it's fine to move to fcitx5 on FACTORY, too.  Recently I
> updated mozc package to support fcitx5 subpackage, too, so it should
> be usable enough for most of Japanese users, too.
> 
> I haven't checked whether all needed fcitx packages have been already
> covered by fcitx5, but I guess major and important ones are already
> there.
> 
> The only concern so far is that both fcitx4 and fctix5 packages are
> exclusive, hence they can't co-exist.  That said, it'll be some "flag
> day" to switch all on Tumbleweed.

BTW, one annoying thing with fcitx5 is that its config tool is now
built with KDE stuff.  When install fcitx5-configtool, it'll drag lots
of KDE-specific things even on XFCE or GNOME.  And it's almost useless
without fcitx5-configtool, so this essentially means the KDE core
stuff becoming de facto mandatory.


Takashi