Path to this page:
./
inputmethod/fcitx5-gtk,
GTK input method module for fcitx5
Branch: CURRENT,
Version: 5.1.1nb12,
Package name: fcitx5-gtk-5.1.1nb12,
Maintainer: ryoonGtk im module for fcitx5 and glib based dbus client library.
Master sites:
Filesize: 52.457 KB
Version history: (Expand)
- (2026-01-07) Updated to version: fcitx5-gtk-5.1.1nb12
- (2025-10-24) Updated to version: fcitx5-gtk-5.1.1nb11
- (2025-09-21) Updated to version: fcitx5-gtk-5.1.1nb10
- (2025-08-31) Updated to version: fcitx5-gtk-5.1.1nb9
- (2025-07-19) Updated to version: fcitx5-gtk-5.1.1nb8
- (2025-07-15) Package has been reborn
CVS history: (Expand)
| 2026-01-07 09:49:50 by Thomas Klausner | Files touched by this commit (2525) |
Log message:
*: recursive bump for icu 78.1
|
| 2025-10-23 22:40:24 by Thomas Klausner | Files touched by this commit (2999) |
Log message:
*: recursive bump for pcre2
Running an old binary against the new pcre doesn't work:
/usr/pkg/lib/libpcre2-8.so.0: version PCRE2_10.47 required by \
/usr/pkg/lib/libglib-2.0.so.0 not defined
|
| 2025-09-21 20:15:09 by Thomas Klausner | Files touched by this commit (56) |
Log message:
*: recursive bump for fmtlib 12
|
| 2025-08-31 00:46:51 by Thomas Klausner | Files touched by this commit (1355) |
Log message:
*: recursive bump for tiff growing lerc dependency
|
| 2025-08-20 13:35:15 by Thomas Klausner | Files touched by this commit (242) |
Log message:
*: fix build with cmake 4
|
| 2025-07-19 07:37:52 by Thomas Klausner | Files touched by this commit (190) |
Log message:
*: bump gobject-introspection users for ABI bump
XXX: I'm actually not sure why the ABI was bumped for 1.84, but now that
it is we have to bump PKGREVISIONs, otherwise pkgin is quite unhappy
|
| 2025-04-24 16:16:37 by Thomas Klausner | Files touched by this commit (2412) |
Log message:
*: recursive bump for jpeg -> libjpeg-turbo switch
|
| 2025-01-24 00:27:30 by Taylor R Campbell | Files touched by this commit (41) |
Log message:
devel/extra-cmake-modules: Use buildlink3.mk, not TOOL_DEPENDS.
This one is borderline: should it be BUILD_DEPENDS or TOOL_DEPENDS?
It doesn't appear to vary depending on the build environment, so it
doesn't meaningfully describe the cross-builder vs the target system.
It is used only at build-time, but it doesn't have any native
executables -- they're just source code cmake scripts.
For now, it is convenient to use a buildlink3.mk file because this
enables us to explicitly expose only files under share/ECM/ -- and
not other random files installed in the prefix -- via buildlink3 to
keep dependent package builds clean. Eventually we should have the
same mechanism for TOOL_DEPENDS but that day has not yet come.
This change creates a new use of BUILDLINK_DEPMETHOD build for
extra-cmake-modules, which is a priori risky. Fortunately,
extra-cmake-modules has no libraries, so this is unlikely to cause
trouble.
|