[MacPorts] #68593: gettext @0.21.1: newer version available

MacPorts noreply at macports.org
Tue Nov 7 15:00:51 UTC 2023


#68593: gettext @0.21.1: newer version available
----------------------+------------------------
  Reporter:  tifrueh  |      Owner:  ryandesign
      Type:  update   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.8.1
Resolution:           |   Keywords:
      Port:  gettext  |
----------------------+------------------------

Comment (by tifrueh):

 I've been trying to write an updated Portfile, but the subport `gettext-
 tools-libs` fails with this message:

 {{{
 :info:build libtool:   error: cannot find the library '../../gettext-
 runtime/intl/libintl.la' or unhandled argument '../../gettext-
 runtime/intl/libintl.la'
 }}}

 It seems to me that the new `gettext` tries to use the included `libintl`
 instead of the previously installed version from `gettext-runtime`, no
 matter what I do.

 I've tried the following configure args, to no avail:

 {{{
 --with-installed-libintl
 --with-libintl-prefix=${prefix}
 }}}

 So I tried to find a bug in `configure.ac`/`Makefile.am`, but wasn't able
 to find anything, probably due to my having no experience with autotools.

 Does anyone more knowledgeable than me have a better idea what's going on
 here?

 ----

 Additionally, I wanted to ask if there is any particular reason why the
 gettext package is split into subports like this. Would it not be simpler
 to build and install the whole package in one go, like the Arch Linux or
 homebrew `gettext` package? That might solve the abovementioned problem.

 Arch Linux
 https://gitlab.archlinux.org/archlinux/packaging/packages/gettext/-/blob/main/PKGBUILD?ref_type=heads

 homebrew https://github.com/Homebrew/homebrew-
 core/blob/a91c41aec30b8454041fdc91d1f028db11927b09/Formula/g/gettext.rb

 ----

 ''Note: Looking at the Arch Linux package I saw that `libtextstyle` is
 being disabled there, due to it depending on `libcroco` which is
 supposedly unmaintained and insecure. Might it be a good idea to do the
 same thing on MacPorts?''

-- 
Ticket URL: <https://trac.macports.org/ticket/68593#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list