On 08/12/2017 07:32 AM, Leonardo Taccari wrote:
Hello D'Arcy, D'Arcy Cain writes:[...] If you add this: .include "../../devel/ncurses/buildlink3.mk" then it will always use ncurses. That would guarantee that it works if built and you can still create a PR to allow it to use the system curses if you want. [...]IMHO this would be a regression for devel/py-curses. Roy has done a great work and AFAIK rtv is the only package problematic due that.
And that is the only package I am suggesting that this be done for.
I think it's better to try to debug and fix it for our curses(3) instead of reverting to use devel/ncurses for py-curses.
As I said, create a PR for that task. I agree that it should work. Meanwhile we would have another package in our pkgsrc.
-- D'Arcy J.M. Cain <darcy%NetBSD.org@localhost> http://www.NetBSD.org/ IM:darcy%Vex.Net@localhost