BSD Ports

devel/gettext-tools 1.0 NetBSD

Tools for providing messages in different languages

System
NetBSD
Repository
pkgsrc
Last update
Commit
c963f82201
License
gnu-gpl-v3
Categories
devel
Package size
3356.2 KiB, 26129.3 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.

This package contains the various development tools. gettextize and autopoint are packaged separately.

In the other systems

SystemPortVersion
NetBSDdevel/gettext-tools1.0
FreeBSDdevel/gettext-tools1.0
DragonFlydevel/gettext-tools0.23.1
MidnightBSDdevel/gettext-tools
HardenedBSDdevel/gettext-tools1.0
GhostBSDdevel/gettext-tools1.0
OPNsensedevel/gettext-tools1.0

Install

Binary package:

pkgin install gettext-tools

From pkgsrc:

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

Packages

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

RepositoryVersion
NetBSD 10.1 x86_641.0
NetBSD 10.1 aarch640.22.5nb1
SmartOS / illumos x86_641.0
macOS 15 arm641.0

Dependencies

Run dependencies 2

Commit history 1

DateCommitCreditsLog message
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 …