Upgrading Pandoc

[Mark Anderson]

Thanks everyone. I hadn't seen that ticket - I've been experimenting with
Haskell and boy getting it to run IS magic. Writing a parser, super easy.
Compiling it? That's a pain.

—Mark
_______________________
Mark E. Anderson <emer at emer.net>

On Wed, Mar 7, 2018 at 6:35 PM, Clemens Lang <cal at macports.org> wrote:

> Hi,
>
> On Sun, Mar 04, 2018 at 02:18:24PM -0500, Mark Anderson wrote:
> > So I started trying to move pandoc from some older version to 2.1.1
> > but then I realized I needed to upgrade the Haskell compiler and
> > libraries to do that. I got started, but wow, this is something else.
> > Does anyone have tips about upgrading Haskell?
>
> I'm attaching my current progress as a patch. It should apply cleanly to
> the current master.
>
> I didn't package stack. It has way too many dependencies to get this
> done without automation, and unless somebody picks up
> https://github.com/neverpanic/cabal2port (or re-writes a similar tool
> from scratch), that's not happening.
>
> Current state of this patch is that I'd need to commit this together
> with a revbump of every haskell port (because otherwise the libraries
> installed by these ports link against libraries built against the old
> GHC, which will not work). That's probably simple enough, so if you want
> to prepare a PR with my changes + the revbumps, that'd be welcome.
>
> Of course, somebody would also have to test build this (or at least some
> large and important haskell ports).
>
> > Is there a magic to it or should I just keep slogging along and open a
> > ticket?
>
> It's magic, unfortunately. ;-)
>
> --
> Clemens
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20180307/31b16c3e/attachment.html>