Issues with oudated ports / GitHub

Marcel Bischoff marcel at
Fri Oct 7 09:15:15 PDT 2016

On 16/10/07, Ryan Schmidt wrote:
>It looks like others have already responded to most of your points, but I would just add:
>On Oct 6, 2016, at 12:12 PM, Marcel Bischoff wrote:
>> But if I still
>> cannot install (for example) pandoc because ghc still requires llwm-3.5
>> which does not compile on Sierra: what choice do I have? I need to get
>> stuff done, not tinker with the infrastructure of my working environment
>> for hours on end, just to get it to work.
>If you just "need to get stuff done, not tinker", then you should not upgrade to a new OS immediately after it is released; wait a month or two. It is inevitable that a new OS release will break some ports, and it will take time for the maintainers of those ports to notice those problems and figure out the solutions, possibly needing to work with the developers of the software to release a new version.

This is stating the obvious. One of my main points was that Homebrew
*does* work and oftentimes has more current packages while MacPorts
*does not*, trying to understand why that is.

>Regarding updating pandoc, see
>Regarding updating ghc, see
>Regarding old llvm on Sierra, see

I have seen all those tickets before. It's basically telling me that
those ports are broken.

More information about the macports-dev mailing list