Re: IBus 1.5

Hello,

 >>> - ibus-* depending on ibus 1.5's typelib (developed in python) is
 >>>
 >>>    not compatible with 1.4.
 >>>    We must update "Requires" tag.
 >>
 >> "not compatible" means it can't be built with 1.5, or it just needs a
 >> proper dependency?

Python is a dynamic language so we can see, for example,
method missing error at runtime. latter one?


 >>> - Do we need to clean up its package's change log while it was
 >>>
 >>>    in the M17N/Devel project?
 >>
 >> The change log must be incremental.  You must not remove the old
 >> changelog that have been already checked in FACTORY, at least.
 >>
 >> So we need to merge the changelog, maybe with a bit of clean up.

The package of ibus-1.5 have been separately developed in M17N/Devel
and not been submitted to Factory.

It has several change log entries for ibus-1.4.99.x.
I think changes from 1.4 to 1.5 is not clear from the log but
it is not so problematic:
https://build.opensuse.org/package/view_file?expand=1&file=ibus.changes&package=ibus&project=M17N%3ADevel
# Oh, it is not linked to M17N/ibus...


 >>> - The released version still have something wrong.
 >>>
 >>>    For example, Ctrl+Space is the only key to toggle IM state but
 >>>    I can see other keys in its dconf profile. (bug or dead code?)
 >>
 >> That's bad.  But maybe fixable during the development?

Maybe.
We can add Zenkaku Hankaku key for Japanese by adding a file to
/etc/dconf/profile but I don't know which binding is active. I'll try.


>> I think we should put all ibus-related packages into a clean sub-project
>> and test them carefully before updating M17N/ibus.
>
> Yes, let's put all ibus-related packages to M17N:Devel at first (just
> do branch or linkpac), then watch the build status.

Unfortunately, since we don't have any rules about M17N:Devel,
it is not clean and has a lot of packages.
# I cannot run zypper dup -r M17N:Devel

Shall we make a new subproject M17N:Testing like openSUSE:*:*:Testing
for packages that should be merged into M17N soon?

Or clean up M17N:Devel?


Hi, Weng,

 > AFAIK this is what it supposed to be. (Though I have nothing to do with IBus
 > dev.. I'm just the one who also keeps an eye on ibus)
 >
 > The new behavior is changed to something like MAC, ctrl+space in ibus-1.5 now
 > behave like alt+tab (kinds of stack based), most recent accessed is the next
 > one being switched by ctrl+space.

I know but I guess the developers try to provide additional keys for switching
stacked IMs for each keyboard layout.


Fuminobu TAKEYAMA

(2012/12/13 5:05), Weng Xuetian wrote:
> On Wednesday 12 December 2012 17:57:28，Takashi Iwai :
>> At Thu, 13 Dec 2012 01:42:25 +0900,
>>
>> Fuminobu TAKEYAMA wrote:
>>> Hi, all,
>>>
>>> IBus 1.5 was released several days ago.
>>> It is major update.
>>
>> Takeyama-san, thanks for heading up.
>> I also wanted to ask about this now, too :)
>>
>>> How do we update packages related to ibus?
>>>
>>> - ibus-* depending on ibus 1.5's typelib (developed in python) is
>>>
>>>    not compatible with 1.4.
>>>    We must update "Requires" tag.
>>
>> "not compatible" means it can't be built with 1.5, or it just needs a
>> proper dependency?
>>
>>> - Compatibility of two versions of libibus is not clear.
>>>
>>>    ibus-mozc linked to 1.4's libibus could communicate with ibus 1.5
>>>    as far as I tested.
>>
>> This is always a potential breakage in every shared library package,
>> and I don't think we can do so much for it.  All related packages in
>> the project (thus later in FACTORY once when ibus-1.5 is checked in)
>> will be rebuilt in anyway, so unless user does strange things, user
>> will get consistent packages from the same project (in theory).
>>
>> But if the backward compatibility isn't kept, basically the shared lib
>> must increase its *.so version number.  If they didn't, it's a clear
>> bug of ibus.
>>
>>> - Do we need to clean up its package's change log while it was
>>>
>>>    in the M17N/Devel project?
>>
>> The change log must be incremental.  You must not remove the old
>> changelog that have been already checked in FACTORY, at least.
>>
>> So we need to merge the changelog, maybe with a bit of clean up.
>>
>>> - The released version still have something wrong.
>>>
>>>    For example, Ctrl+Space is the only key to toggle IM state but
>>>    I can see other keys in its dconf profile. (bug or dead code?)
>>
>> That's bad.  But maybe fixable during the development?
>
> AFAIK this is what it supposed to be. (Though I have nothing to do with IBus
> dev.. I'm just the one who also keeps an eye on ibus)
>
> The new behavior is changed to something like MAC, ctrl+space in ibus-1.5 now
> behave like alt+tab (kinds of stack based), most recent accessed is the next
> one being switched by ctrl+space.
>
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]