#48852 closed update (wontfix)
Please update ncurses to version 6.0-20150912
| Reported by: | gallafent | Owned by: | jmroot (Joshua Root) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.3.3 |
| Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia) | |
| Port: | ncurses |
Description
As per http://lists.gnu.org/archive/html/bug-ncurses/2015-09/msg00007.html there is a release of ncurses which improves build robustness (particularly when using clang) on Mac OS X :)
Thanks due to Mr. Dickey for the quick fix!
Change History (4)
comment:1 Changed 9 years ago by jmroot (Joshua Root)
| Cc: | jeremyhu@… added; jmr@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to jmr@… |
comment:2 Changed 9 years ago by gallafent
I can't see that revision directly (trac says “No changeset 140232 in the repository”) but can confirm that the current state of the ncurses port does indeed appear to build and install for me with my config now that I've deleted my local hack to the portfile in my local repository!
That makes this update less urgent for me of course, but perhaps it would be as well to update to current upstream release in any case, possibly reducing the amount of patching macports has to do before building?
comment:3 Changed 9 years ago by jmroot (Joshua Root)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
There is no new upstream release. The maintainer makes development snapshots available, and that's what the 20150912 tarball is. Since Jeremy's fix works, I think we'll just leave it as is, for now at least.
comment:4 Changed 9 years ago by gallafent
Ah, good point. That'll be me misunderstanding ncurses' release process then! :) … it's of course completely fine from my perspective to leave things as they are until ncurses 6.1 is released!
Doesn't r140232 already fix this?