Hello community,

here is the log from the commit of package ibus-pinyin for openSUSE:Factory 
checked in at 2012-06-01 22:30:56
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/ibus-pinyin (Old)
 and      /work/SRC/openSUSE:Factory/.ibus-pinyin.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "ibus-pinyin", Maintainer is ""

Changes:
--------
--- /work/SRC/openSUSE:Factory/ibus-pinyin/ibus-pinyin.changes  2012-03-22 
12:33:04.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.ibus-pinyin.new/ibus-pinyin.changes     
2012-06-01 22:31:41.000000000 +0200
@@ -1,0 +2,6 @@
+Fri Jun  1 23:09:14 UTC+8 2012 - [email protected]
+
+- enable opencc support
+- fix build in Factory
+
+-------------------------------------------------------------------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ ibus-pinyin.spec ++++++
--- /var/tmp/diff_new_pack.L7r6ph/_old  2012-06-01 22:31:43.000000000 +0200
+++ /var/tmp/diff_new_pack.L7r6ph/_new  2012-06-01 22:31:43.000000000 +0200
@@ -29,13 +29,14 @@
 Source1:        
http://scim-python.googlecode.com/files/pinyin-database-1.2.99.tar.bz2
 Patch:          ibus-pinyin-fsf-address.diff
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
-BuildRequires:  gcc-c++ gettext-devel libuuid-devel sqlite3-devel
+BuildRequires:  gcc-c++ gettext-devel libuuid-devel sqlite3 opencc-devel 
sqlite3-devel
 BuildRequires:  python >= 2.5
 BuildRequires:  intltool
 BuildRequires:  boost-devel
 BuildRequires:  ibus-devel
 Requires:       ibus
 
+
 %description
 PinYin engine for IBus platform. It provides a Chinese PinYin input method.
 
@@ -50,7 +51,8 @@
 
 %build
 %configure --disable-static \
-           --enable-db-open-phrase \
+           --enable-db-open-phrase\
+           --enable-opencc\
           --libexecdir=%{_prefix}/%{_lib}/ibus
 
 # make -C po update-gmo

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to