Subject: Re: USE_NCURSES? [was: Re: CVS commit: pkgsrc]
To: None <>
From: Greg A. Woods <>
List: tech-pkg
Date: 10/22/1999 14:55:34
[ On Friday, October 22, 1999 at 22:24:58 (+1000), Simon Burge wrote: ]
> Subject: Re: USE_NCURSES? [was: Re: CVS commit: pkgsrc] 
> Hubert Feyrer wrote:
> > 
> > i think you can add this for about any package that wants ncurses. 
> > Should we add some USE_NCURSES switch that hides these bits in 
> > 
> > .if defined(USE_NCURSES)
> > .if ${OPSYS} == "NetBSD"
> > DEPENDS+=      ncurses-4.2:../../devel/ncurses
> > .endif # NetBSD
> > .endif # USE_NCURSES
> Maybe USE_SVID_CURSES would be a better choice.  Both ncurses and SysV
> curses comply with the SVID standard for curses, and we (NetBSD) have
> people aiming to take our curses to the standard as well.  Just calling
> the option USE_NCURSES seems a bit restrictive...

If NetBSD curses is to become SVID compliant then calling it USE_NCURSES
seems to make perfect sense (i.e. to signify a direct dependence on some
specific ncurses feature) and to call it USE_SVID_CURSES would seem
totally redundant and would miss the point entirely (i.e. would prevent
one from indicating a specific ncurses dependency).

It might be good to have a separate meaning for USE_SVID_CURSES though
-- one that could be used for packages that need SVID support, but don't
care particularly if they get it from ncurses, SunOS-5 (zoularis), or
eventually NetBSD curses once it's SVID-compliant.

							Greg A. Woods

+1 416 218-0098      VE3TCP      <>      <robohack!woods>
Planix, Inc. <>; Secrets of the Weird <>