lttoolbox: upgrade to 3.7.6, apertium: upgrade to 3.9.4 #27417
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
These ports have not been updated in several years. I am not sure if old and new versions work well together, so I thought it would be best to update them both in the same PR. They are separate ports even though both are part of the Apertium project, so there are two commits. Please let me know if I should squash them.
Both have migrated from SourceForge to GitHub. They now require C++17 (apertium needs LegacySupport for
std::filesystem
on Darwin < 19) and build with autoreconf. I have also updated the dependencies.For
lttoolbox
I had to add dependenciesautoconf
,automake
andlibtool
even though I putuse_autoreconf
in the Portfile. That was not necessary forapertium
, and doing it would even haveport lint
complain about duplicate dependencies. I have no idea why.Type(s)
Tested on
macOS 10.9.5 13F1911 x86_64
Xcode 6.2 6C131e
Verification
Have you
port lint
?sudo port test
?sudo port -vst install
?Tested some binaries, to check for linker errors. Both ports install quite a few binaries and I do not know how to use all of them.