Re: IBus 1.5

(2012/12/14 16:47), Takashi Iwai wrote:
> (And basically testing here at this moment means checking mostly build
> breakage.  The functional test is a different question.)

What we are doing for ibus looks like functional test.

> If we care about the stability of M17N packages, it's the thing we
> need to reconsider.  M17N project serves as the devel project of
> FACTORY, thus it should contain the latest packages to be merged to
> FACTORY.  It conflicts with the development of new packages.

I think stability of obs (including devel) projects will become more
important. Actually many people use latest packages from those projects.
This scenario is a benefit of our obs-style distribution development.
Also I think to reduce factory team's workload, more careful review and
test in devel project is needed.

But if we need to submit developing packages to factory like KDE and GNOME,
we have to separate stable/unstable packages as you say.


Next is a technical topic.
Can we use %posttrans in zypper or rewrite other tags?

According to Fedora's spec [1], written by an upstream developer,
we need:

> %posttrans
> gtk-update-icon-cache %{_datadir}/icons/hicolor &>/dev/null || :
> glib-compile-schemas %{_datadir}/glib-2.0/schemas &>/dev/null || :
> dconf update


"dconf update" is especially important. It initializes database for ibus's
configuration. Since our current package doesn't have this, it should not
work correctly until we run "sudo dconf update" manually.

We also need to add "dconf update" into %postun to remove the db.
>   # 'dconf update' sometimes does not update the db...
>   dconf update
>   if [ -f %{_sysconfdir}/dconf/db/ibus ] ; then
>       rm -f %{_sysconfdir}/dconf/db/ibus
>   fi

[1] http://pkgs.fedoraproject.org/cgit/ibus.git/tree/ibus.spec

I have just added a patch from ibus's git head to fix ibus-setup crash.
I guess ibus-1.5.2 will be released soon.

--
Fuminobu TAKEYAMA
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]