[MacPorts] #58526: gettext: 0.20.1 was released
MacPorts
noreply at macports.org
Tue May 12 02:55:44 UTC 2020
#58526: gettext: 0.20.1 was released
----------------------+------------------------
Reporter: akimd | Owner: ryandesign
Type: update | Status: accepted
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: gettext |
----------------------+------------------------
Changes (by ryandesign):
* cc: jmroot (added)
Comment:
Replying to [comment:10 akimd]:
> I don't know what these -bootstrap ports are for.
We want to build everything using libc++ on Mac OS X 10.6 and later, but
Mac OS X 10.6 does not provide libc++; we have to build it and install it.
There is a chicken and egg problem: how could you build libc++'s
dependencies using libc++ if there is no libc++ yet? The answer was to
provide "bootstrap" versions of libc++'s dependencies that would use
libstdc++ instead of libc++. gettext is one of those dependencies.
It could be argued that for the bootstrap ports we should disable as much
optional functionality as possible, since they're just for us to use to
build libc++ and are not intended for users to use directly, and that that
might include natural language support provided by gettext. I wasn't
involved with [changeset:640b7e0aa8710d26cd0af15bde29bb6290ad6b20
/macports-ports the creation of the bootstrap ports] so I don't know why
that wasn't done, but it would introduce additional complexity into the
bootstrap ports. Maybe it was felt to be better to keep the bootstrap and
non-bootstrap versions of the ports as similar as possible.
Joshua, do you recall whether it was considered to disable gettext support
in the bootstrap ports so that we wouldn't need to have a gettext-
bootstrap port?
--
Ticket URL: <https://trac.macports.org/ticket/58526#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list