Subject: Re: bash should depend on ncurses under Linux
To: Jeremy C. Reed <email@example.com>
From: Todd Vierling <firstname.lastname@example.org>
Date: 10/25/2003 19:28:58
On Sat, 25 Oct 2003, Jeremy C. Reed wrote:
: I don't know what it will do under SunOS or Slackware or Red Hat (which
: usually have bash using libtermcap also).
However, the two Linuxen you mention normally also ship with ncurses, so the
buildlink2.mk would typically be a no-op on those systems.
Under SunOS (and IRIX and Darwin) it will pull in ncurses wholesale. It's
probably very likely that SunOS 5.something should be in the list of
"compatible" replacements, and there's a comment to that effect in
# This catch-all for SunOS is probably too broad, but better to err on
# the safe side. We can narrow down the match when we have better
I think that it should be OK to pull in ncurses/buildlink2.mk in bash, and
let someone who cares on SunOS provide the "better information" above to
make the _INCOMPAT_CURSES definition more granular. The SysV curses API is
a bit richer than BSD's, so Solaris's curses should (in theory) be even more
usable as a ncurses substitute than NetBSD's.
-- Todd Vierling <email@example.com> <firstname.lastname@example.org>