[MacPorts] #54855: Bug introduced in ncurses 6.0+20170701 is fixed upstream

[MacPorts]

#54855: Bug introduced in ncurses 6.0+20170701 is fixed upstream
-------------------------+----------------------
  Reporter:  grumpybozo  |      Owner:  jmroot
      Type:  update      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:  haspatch
      Port:  ncurses     |
-------------------------+----------------------

Comment (by lbschenkel):

 I found it strange that you could not reproduce it (since I can reproduce
 it 100% in any platform), so I tested again. I discovered that the
 subsequent (and currently latest) terminfo release, 1.617, does not
 trigger the crash. Rolling back to the previous one, 1.616, does crash.

 So I suppose that an upgrade to latest ncurses (or any recent version that
 ships with terminfo 1.617) should be "safe" from a NeoVim point of view.
 Since NeoVim 0.2.0 terminfo parsing code is buggy, it's hard to tell which
 changes/combinations of factors in terminfo will cause it to dump core on
 start.

 To make it a bit easier to handle these kind of situations in the future,
 it may be worth considering splitting the terminal database from ncurses
 into its own port, `terminfo`, so the code and the terminal definitions
 could be upgraded independently. Linux distros in particular often ship
 both as separate packages for this reason.

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