Edit Package ibus

An Intelligent Input Bus

https://github.com/ibus/ibus/

IBus is an Intelligent Input Bus. It is a new input framework for Linux OS.
It provides full featured and user friendly input method user interface.
It also may help developers to develop input method easily.

Refresh
Refresh
Source Files (show merged sources derived from linked package)
Filename Size Changed
README.SUSE 0000003323 3.25 KB over 1 year
_multibuild 0000000054 54 Bytes 6 months
baselibs.conf 0000000992 992 Bytes 6 months
hide-setup-menu.patch 0000000389 389 Bytes almost 3 years
ibus-1.5.26.tar.gz 0003715263 3.54 MB 3 months
ibus-autostart 0000000231 231 Bytes over 6 years
ibus-autostart.desktop 0000000327 327 Bytes over 1 year
ibus-disable-engines-preload-in-GNOME.patch 0000000937 937 Bytes about 5 years
ibus-fix-Signal-does-not-exist.patch 0000000513 513 Bytes over 2 years
ibus-fix-refcounting-issues.patch 0000009194 8.98 KB 2 months
ibus-socket-name-compatibility.patch 0000007669 7.49 KB 10 months
ibus-xim-fix-re-focus-after-lock.patch 0000000511 511 Bytes about 8 years
ibus.changes 0000053009 51.8 KB 2 months
ibus.spec 0000014399 14.1 KB 2 months
im-engines-precede-xkb.patch 0000000914 914 Bytes over 7 years
macros.ibus 0000001073 1.05 KB almost 8 years
setup-switch-im.patch 0000002824 2.76 KB 10 months
xim.d-ibus-121 0000001572 1.54 KB almost 2 years
xim.ibus.suse.template 0000000739 739 Bytes over 12 years
Comments 5

Marguerite Su's avatar

MargueriteSu wrote almost 4 years ago

@ftake

Can you please explain why python3-ibus was dropped? I read the changelog, but I didn't understand the "upstream will not maintain it for python 3" sentence. if so, why upstream still accept my ibus-force-python3.patch?

As we know, openSUSE is disgarding python 2.x, and that's why @qzhao dropped ibus-sunpinyin and ibus-googlepinyin from openSUSE:Factory. If ibus upstream "will not maintain it for python3", then python-ibus will be dropped soon because the engines require it have been dropped.

@qzhao actually I tested the python3-ibus in Leap 15.0, after patching "import gobject" further, it's usable. I also tested ibus-sunpinyin (because I think it's still been using by our users), it worked well with python3-ibus and python3-gobject2 without any modification since it's really a small setup program.

So I think here's the thing:

ftake and qzhao are different in view. qzhao wanted to follow our python 2.x removal progress while ftake wanted to keep python-ibus as it is.

both have troubles for now. for ftake, python-ibus will be dropped anyway. for qzhao, you didn't test if some engines are portable...

Greetings

Marguerite


Fuminobu Takeyama's avatar

ftake wrote almost 4 years ago

@MargueriteSu

At the previous update, I specified a new flag --disable-python2 introduced by the upstream. Then, that flag removes what we have called python3-ibus.

Now Python application can communicate by using IBus gobject introspection without python3-ibus. So only legacy application, which is/was written in Python 2, might be using that library.

So I asked "Do we still need python3-ibus?" before submitting the previous update. ibus-sunpinyin still requires python3-ibus? Is it possible to remove that dependency by patching to ibus-sunpinyin?


Fuminobu Takeyama's avatar

ftake wrote almost 4 years ago

Sorry, I just asked do we still need python(2)-ibus.


Fuminobu Takeyama's avatar

ftake wrote almost 4 years ago

About "ibus-force-python3.patch", "--disable-python2" allow us to build ibus without python2. And the patch was not merged as it is, implemented different way.


Cliff Zhao's avatar

qzhao wrote almost 4 years ago

Sorry, could you please show me the discussion record of my opinion? My memory of the context was a little hazy.

openSUSE Build Service is sponsored by