On Thu, 20 Feb 2003 11:59:09 -0800 (PST)
"Jeremy C. Reed" <reed@reedmedia.net> wrote:

> > Why do you need this?? Simply include the ncurses/buildlink2.mk file directly
> > and let buildlink2 do its magic.
> 
> That's part of the problem. Many packages using curses or ncurses don't
> even have any
> .include "../../devel/ncurses/buildlink2.mk"
> line.

So they should.

> > And here is the problem: That buildlink2.mk should be fixed to check if the
> > system provides a native curses, and iff it doesn't, then unconditionally use
> > ncurses (setting UE_NCURSES), so we get a dependancy.
> 
> That would be good. Thanks for thinking about this, Julio.

I'm sure jlam has something to say about this.  Just wait ;)

> No, they have it. (The build OS may have a valid install-info, so it
> doesn't register the DEPENDS.) I just send-pr'd a simple patch: pkg/20450.

Ok, thanks.

-- 
Julio M. Merino Vidal <jmmv@menta.net>
The NetBSD Project - http://www.NetBSD.org/