BSD Ports

devel/gettext 1.0 NetBSD

Tools for providing messages in different languages

System
NetBSD
Repository
pkgsrc
Last update
Commit
616d7c10fe
License
gnu-gpl-v3
Categories
devel
Package size
27.4 KiB, 173.7 KiB installed

Description

GNU gettext provides the necessary tools and libraries for handling messages in different languages, as one of the steps to internationalisation (or i18n) of a utility.

In the other systems

SystemPortVersion
NetBSDdevel/gettext1.0
FreeBSDdevel/gettext1.0
OpenBSDdevel/gettext1.0
DragonFlydevel/gettext0.23.1
MidnightBSDdevel/gettext

Install

Binary package:

pkgin install gettext

From pkgsrc:

cd /usr/pkgsrc/devel/gettext && make install clean

Dependencies

Run dependencies 4

No port depends on this one.

Commit history 4

DateCommitCreditsLog message
616d7c10fe tnn *: Fix inaccurate comments about iconv detection on macOS
The detection is not faulty; the implementation is rejected with intent. Issue will need a generic pkgsrc resolution at some point.
647d8a3436 tnn gettext-tools: do not autodetect libcurl and libjson-c
Fixes build on OpenIndiana. The libraries are shipped with base but at least some of the headers seem absent.
d1aeddbfa7 jperkin gettext: Add missing USE_INCLUDED_LIBINTL patch.
Fixes build of gettext-tools. While here try to reduce some pkglint.
c963f82201 adam gettext: updated to 1.0
Version 1.0 - January 2026 Improvements for maintainers and distributors: * In a po/ directory, the PO files are now exactly those that the translators submitted or committed in version control, or a translation project's daemon committed on behalf of the translators. They are no longer regularly updated with respect to the POT file in the same directory. The advantage for maintainers is that the maintainer may commit the PO files in version control, without getting - lots of modified files shown by "git status", - frequent merge conflicts when merging between branches, - a voluminous version control history. The advantage for distributors is that the role of files in a release tarball are clearer: The PO files are source code, whereas …