Comment 13 for bug 1547816

Revision history for this message
Mitsuya Shibata (cosmos-door) wrote : Re: Merge mozc (2.17.2116.102+gitfd0f5b34+dfsg-1ubuntu1) from Debian unstable (main)

Hi all,

This is caused by more complex reasons of differencies between two versions of mozc.

* Mozc switched from Google Code/svn to GitHub/git.
* Mozc introduced git-submodules for some packages in src/third_party/ directory.
  * added .gitmodules file
  * NOTE: Mozc in old svn has included all codes for third_party directory.
* mozc package in debian isn't include .gitmodule in upstream branch.
  * its a bug of git-buildpackage or uupdate?
* mozc package in debian dropped binaries in third_party directory for DFSG compliant.
  * from 2.16.2116.102, dfsg flag is added in the version string.
  * therefore, third_party directory became empty and removed.

* src/third_party/{gmock, gtest, jsoncpp} are used only to run test.
  * mozc package in debian doesn't call 'src/build_mozc.py runtests'.
  * mozc package in ubuntu call 'src/build_mozc.py runtests'.
    * it was added by Aron Xu.
* gmock and gtest are depended by allmost tests.
  * i.e. cannot drop 'some' tests which depends gmock/gtest, can only drop 'all' test.
* jsoncpp is used only for network test.
* gtest and jsoncpp is packaged in main and gmock is not packaged.
  * NOTE: Mozc needs source package of jsoncpp, doesn't binary package.
  * gmock was merged to gtest in upstream, but new gtest isn't released yet.

Conclusion:
We should drop runtest as same as Debian.

Is this conclusion acceptable for package in main component?