Arch Linux User Repository

If you're getting compilation errors, please delete your Bazel cache (~/.cache/bazel by default).

So both packages build from the same upstream source, but apart from the additional dictionaries they include, the only difference is that this package is stuck on a old commit, where-as ibus-mozc-ut is using a more recent commit?

Also since mozc does not tag releases then it is up to the PKGBUILD maintainer to update the package at an appropriate commit in order to keep it up to date?

In that case I hope you are successful in getting ownership of this package! I will be moving to ibus-mozc-ut for the time being.

@CyberShadow Hmm, now that you mention it... There is of course the issue that my ibus-mozc-ut package includes the unofficial UT dictionary, so it's not a one for one replacement for the vanilla ibus-mozc, but since the base Mozc functionality (along with the UT inclusion) has been split into its own package, there really isn't anything that precludes merging them all into a family of interchangeable packages.

Well, back when I created my package I didn't want to step on anyone's toes (let alone @ponsfoot's, who'd been the de facto maintainer of the Mozc AUR packages for ages) but I think you're right, this probably calls for an orphan-and-adopt procedure. Thanks for the tip.

Nocifer, I think the appropriate procedure for this case is to submit a request to orphan this package and adopt it. If this package provides zero benefit over existing packages, then it could also be deleted, with the better packages having provides/replaces=mozc to provide an upgrade path.

Hey guys, I hope you all are aware that this package was last updated some 3 years ago and is currently unmaintained and severely out of date? I'm not usually one to tout my own horn, but there does exist an updated version in the AUR that is actively maintained (currently by me; that's the proverbial horn) and which solves the issues I see mentioned here, both the dependency on gtk2 (that's been deprecated and removed by upstream since ages ago, along with the python2 dependency) and the conflict between ibus-mozc and fcitx-mozc (you can have both installed on your system at the same time).

The updated package is ibus-mozc-ut. And again, because I dislike touting my own horn, let me just say that it's not like I stand to gain something by posting this "ad" here, it's just that the whole reason I created a new package in the first place was to spare people (myself included) from exactly the kind of issues reported in the comments here.

Just a friendly FYI.

please add gtk2 as a dependency? that fixed it for me aswell

Installing the gtk2 package resolved the build issue mentioned by @CyberShadow for me.

Seems to fail finding gtk+:

INFO: Running: /usr/bin/python2 /build/mozc/src/mozc/src/third_party/gyp/gyp_main.py --depth=. --include=./gyp/common.gypi -D abs_depth=/build/mozc/src/mozc/src -D ext_third_party_dir=/build/mozc/src/mozc/src/third_party -D python_executable=/usr/bin/python2 ./base/base.gyp ./base/base_test.gyp ./client/client.gyp ./client/client_test.gyp ./composer/composer.gyp ./composer/composer_test.gyp ./config/config.gyp ./config/config_test.gyp ./converter/converter.gyp ./converter/converter_base.gyp ./converter/converter_main.gyp ./converter/converter_test.gyp ./data/test/session/scenario/scenario.gyp ./data/test/session/scenario/usage_stats/usage_stats.gyp ./data_manager/chromeos/chromeos_data_manager.gyp ./data_manager/chromeos/chromeos_data_manager_base.gyp ./data_manager/chromeos/chromeos_data_manager_test.gyp ./data_manager/data_manager.gyp ./data_manager/data_manager_base.gyp ./data_manager/data_manager_test.gyp ./data_manager/oss/oss_data_manager.gyp ./data_manager/oss/oss_data_manager_base.gyp ./data_manager/oss/oss_data_manager_test.gyp ./data_manager/testing/mock_data_manager.gyp ./data_manager/testing/mock_data_manager_base.gyp ./data_manager/testing/mock_data_manager_test.gyp ./dictionary/dictionary.gyp ./dictionary/dictionary_base.gyp ./dictionary/dictionary_test.gyp ./dictionary/file/dictionary_file.gyp ./dictionary/file/dictionary_file_test.gyp ./dictionary/system/system_dictionary.gyp ./dictionary/system/system_dictionary_test.gyp ./engine/engine.gyp ./engine/engine_test.gyp ./gui/gui.gyp ./gyp/tests.gyp ./handwriting/handwriting.gyp ./handwriting/handwriting_test.gyp ./handwriting/zinnia.gyp ./ipc/ipc.gyp ./mac/mac.gyp ./net/jsoncpp.gyp ./net/net.gyp ./net/net_test.gyp ./prediction/prediction.gyp ./prediction/prediction_base.gyp ./prediction/prediction_test.gyp ./protobuf/protobuf.gyp ./protocol/protocol.gyp ./renderer/renderer.gyp ./request/request.gyp ./rewriter/calculator/calculator.gyp ./rewriter/rewriter.gyp ./rewriter/rewriter_base.gyp ./rewriter/rewriter_test.gyp ./server/server.gyp ./session/session.gyp ./session/session_base.gyp ./session/session_test.gyp ./storage/storage.gyp ./storage/storage_test.gyp ./testing/testing.gyp ./transliteration/transliteration.gyp ./transliteration/transliteration_test.gyp ./unix/emacs/emacs.gyp ./unix/ibus/ibus.gyp ./usage_stats/usage_stats.gyp ./usage_stats/usage_stats_base.gyp ./usage_stats/usage_stats_test.gyp -D branding=Mozc -D use_qt=YES -D qt_dir= -D use_wix=NO -D build_base=/build/mozc/src/mozc/src/out_linux -D build_short_base=out_linux -D warn_as_error=0 -D channel_dev=1 -D enable_cloud_handwriting=0 -D target_platform=Linux -D use_libibus=1 --generator-output=. -G output_dir=out_linux
Package gtk+-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtk+-2.0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'gtk+-2.0', required by 'virtual:world', not found
Package 'gdk-2.0', required by 'virtual:world', not found
gyp: Call to 'pkg-config --libs-only-l glib-2.0 gobject-2.0 gthread-2.0 gtk+-2.0 gdk-2.0' returned exit status 1 while in renderer/renderer.gyp.
Traceback (most recent call last):
  File "build_mozc.py", line 1236, in <module>
    main()
  File "build_mozc.py", line 1220, in main
    GypMain(cmd_opts, cmd_args)
  File "build_mozc.py", line 736, in GypMain
    RunOrDie(gyp_command + gyp_options)
  File "/build/mozc/src/mozc/src/build_tools/util.py", line 99, in RunOrDie
    '==========']))
build_tools.util.RunOrDieError: 
==========
 ERROR: /usr/bin/python2 /build/mozc/src/mozc/src/third_party/gyp/gyp_main.py --depth=. --include=./gyp/common.gypi -D abs_depth=/build/mozc/src/mozc/src -D ext_third_party_dir=/build/mozc/src/mozc/src/third_party -D python_executable=/usr/bin/python2 ./base/base.gyp ./base/base_test.gyp ./client/client.gyp ./client/client_test.gyp ./composer/composer.gyp ./composer/composer_test.gyp ./config/config.gyp ./config/config_test.gyp ./converter/converter.gyp ./converter/converter_base.gyp ./converter/converter_main.gyp ./converter/converter_test.gyp ./data/test/session/scenario/scenario.gyp ./data/test/session/scenario/usage_stats/usage_stats.gyp ./data_manager/chromeos/chromeos_data_manager.gyp ./data_manager/chromeos/chromeos_data_manager_base.gyp ./data_manager/chromeos/chromeos_data_manager_test.gyp ./data_manager/data_manager.gyp ./data_manager/data_manager_base.gyp ./data_manager/data_manager_test.gyp ./data_manager/oss/oss_data_manager.gyp ./data_manager/oss/oss_data_manager_base.gyp ./data_manager/oss/oss_data_manager_test.gyp ./data_manager/testing/mock_data_manager.gyp ./data_manager/testing/mock_data_manager_base.gyp ./data_manager/testing/mock_data_manager_test.gyp ./dictionary/dictionary.gyp ./dictionary/dictionary_base.gyp ./dictionary/dictionary_test.gyp ./dictionary/file/dictionary_file.gyp ./dictionary/file/dictionary_file_test.gyp ./dictionary/system/system_dictionary.gyp ./dictionary/system/system_dictionary_test.gyp ./engine/engine.gyp ./engine/engine_test.gyp ./gui/gui.gyp ./gyp/tests.gyp ./handwriting/handwriting.gyp ./handwriting/handwriting_test.gyp ./handwriting/zinnia.gyp ./ipc/ipc.gyp ./mac/mac.gyp ./net/jsoncpp.gyp ./net/net.gyp ./net/net_test.gyp ./prediction/prediction.gyp ./prediction/prediction_base.gyp ./prediction/prediction_test.gyp ./protobuf/protobuf.gyp ./protocol/protocol.gyp ./renderer/renderer.gyp ./request/request.gyp ./rewriter/calculator/calculator.gyp ./rewriter/rewriter.gyp ./rewriter/rewriter_base.gyp ./rewriter/rewriter_test.gyp ./server/server.gyp ./session/session.gyp ./session/session_base.gyp ./session/session_test.gyp ./storage/storage.gyp ./storage/storage_test.gyp ./testing/testing.gyp ./transliteration/transliteration.gyp ./transliteration/transliteration_test.gyp ./unix/emacs/emacs.gyp ./unix/ibus/ibus.gyp ./usage_stats/usage_stats.gyp ./usage_stats/usage_stats_base.gyp ./usage_stats/usage_stats_test.gyp -D branding=Mozc -D use_qt=YES -D qt_dir= -D use_wix=NO -D build_base=/build/mozc/src/mozc/src/out_linux -D build_short_base=out_linux -D warn_as_error=0 -D channel_dev=1 -D enable_cloud_handwriting=0 -D target_platform=Linux -D use_libibus=1 --generator-output=. -G output_dir=out_linux
==========
==> ERROR: A failure occurred in build().
    Aborting...

Missing dependency?

@cobaltspace :

To avoid conflict with fcitx-mozc,

Option A. Modify fcitx-mozc (community) package to build mozc_emacs_helper with it.

Option B. Or, remove conflicted modules from mozc (AUR) package.

Both ways need to edit PKGBUILD by yourself.

For Option A, following posts are useful (if you can read or translate Japanese).

https://qiita.com/yutopp/items/7e042c04331b47506e95 , https://noyuno.github.io/2018-06-01-mozc

And, there is modified PKGBUILD at https://github.com/nozaki87/svntogit-community/blob/fcitx-mozc-w-emacshelper/fcitx-mozc/trunk/PKGBUILD .

You can use this PKGBUILD off-the-shelf at your own risk.

For Option B, there are good posts (also written in Japanese).

http://ain0204.hatenablog.com/entry/2016/08/12/235206 , https://qiita.com/hattorix@github/items/909df7f4bf01e57320c0

Sorry if this is off-topic...

Is there a way to not conflict with fcitx-mozc?