BSD Ports

japanese/fcitx5-mozc 3.35.6354.101_1 FreeBSD

Mozc engine for Fcitx 5

System
FreeBSD
Repository
FreeBSD ports
Maintainer
[email protected]
Port added
Last update
Commit
a6083c2eb0
Categories
japanese

Description

Mozc engine for Fcitx 5

Install

Binary package:

pkg install ja-fcitx5-mozc

From the ports tree:

cd /usr/ports/japanese/fcitx5-mozc/ && make install clean

To depend on this port in another port's Makefile:

RUN_DEPENDS=	ja-fcitx5-mozc>0:japanese/fcitx5-mozc

Packages

The version each package repository carries. “-” means the repository builds no package of it, “n/a” that there is no such repository.

Repositoryaarch64amd64armv6armv7i386
FreeBSD:14:latest-3.35.6354.101_1---
FreeBSD:14:quarterly--n/a--
FreeBSD:15:latest3.35.6354.101_13.35.6354.101_1n/a--
FreeBSD:15:quarterly--n/an/an/a
FreeBSD:16:latest--n/an/an/a
FreeBSD:16:quarterlyn/an/an/an/an/a

Dependency graph

Ports that need it on the left, what it needs to run on the right; at most 8 of each. "Dependencies" below lists them all.

Dependencies

The Makefile names none itself; they come from USES and USE_*.

The full lists below include those, and their dependencies in turn.

Build dependencies 90
Run dependencies 136

The first 100 are listed.

No port depends on this one.

Configuration

No options to configure.

Service scripts
none

Files

No file lists for this port.

Commit history 1

DateCommitCreditsLog message
a6083c2eb0 Hiroki Sato japanese/mozc-server: Update from 2.23.2815.102.01 to 3.35.6354.101
- Adapt FreeBSD support and installation paths to the updated sources. - Use the base system's zlib and ports-provided Python, Qt 6, and input method framework libraries. - Add a static list of distfiles required by Bazel 9 to avoid network downloads during the build. - Update the IBus and uim frontends, and replace Fcitx 4 support with Fcitx 5. - Share icons installed by mozc-server with the input method frontends. - Fix Emacs input method registration and make mozc_emacs_helper available in PATH. This allows mozc.el from MELPA to work without additional configuration. - Update startup scripts, package messages, and license declarations. - Preserve license texts and copyright notices for bundled components.