[Bug 194038] New: [exp-run] update and split up devel/gettext and USES=gettext
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Sep 30 11:56:27 UTC 2014
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194038
Bug ID: 194038
Summary: [exp-run] update and split up devel/gettext and
USES=gettext
Product: Ports Tree
Version: Latest
Hardware: Any
OS: Any
Status: Needs Triage
Severity: Affects Only Me
Priority: ---
Component: Infrastructure
Assignee: freebsd-ports-bugs at FreeBSD.org
Reporter: tijl at FreeBSD.org
Created attachment 147839
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=147839&action=edit
patch
In the gettext distfile there's a file named PACKAGING which recommends to
split up the gettext package into gettext-runtime (libintl) and gettext-tools
(development/translation tools). Normally subpackages would be used for this,
but since the distfile basically consists of two subdirectories each with their
own configure script it is relative easy to create separate ports.
Moreover, there's a minor issue with the combination of USES=autoreconf with
USES=gettext hidden behind an NLS option. If a port uses gettext, autoreconf
requires autopoint (part of gettext-tools) even if the NLS option is off. A
port like net-mgmt/nagios-plugins now does the following:
USES= autoreconf
NLS_USES= gettext
NLS_USES_OFF= gettext:build
This isn't very intuitive and I've had people asking questions about this. It
could be made more elegant by splitting up USES=gettext into
USES=gettext-runtime and USES=gettext-tools that correspond to the ports. Then
you would have:
USES= autoreconf gettext-tools
NLS_USES= gettext-runtime
The attached patch splits up devel/gettext into devel/gettext-runtime and
devel/gettext-tools and USES=gettext into USES=gettext-runtime and
USES=gettext-tools. It leaves devel/gettext as a meta port/package and
USES=gettext as a meta USES. The ports are updated to version 0.19.2.
The patch also removes :oldver from gettext-runtime and libiconv. To prevent
bumping PORTREVISION on a lot of ports they still install a symlink with the
old .so version. As soon as most ports that depend on them have had an version
update (for other reasons) the remaining ports (small number) can get a
PORTREVISION bump and these links can be removed.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list