I haven't been around much (too busy with work and life) but I thought
I'd comment on this. I do not see any reason not to make ncurses a
requirement for epic5. Everyone should expect changes in epic5, and
this dependency should not cause any problems. I cannot think of any
system I've been on that does not have curses installed, and we already
require either terminfo/curses or termcap. Maybe we should take a poll
to see if anyone uses epic on a system that does not have ncurses, just
to see if this is an issue for anyone.
RoboHak
Jeremy Nelson wrote:
Well, I was going to have to bring this issue up at some point, and so it
might as well be now.
Up throughout its lifetime, epic has never had any "mandatory dependancies",
which just means another piece of software that absolutely must be installed
before epic will build. EPIC has many "optional dependancies" (perl, tcl,
socks, ssl, and so on), but you're not required to take them.
But now I am at a place where it seems to really move forward with the
interface, it is necessary to make epic a curses program, particularly to
use libpanel[1]. This makes a dependance on sysv curses (ncurses) a
mandatory dependance. This is a big step.
How do you all feel about making curses a mandatory dependancy for epic5?
System V Curses (ncurses) is a very widely deployed, but not necessarily
universally available thing.
Jeremy
[1] libpanel is a library wrapper on top of sysv curses that implements a
3-dimensional multiple document interface (mdi).
_______________________________________________
List mailing list
List@epicsol.org
http://epicsol.org/mailman/listinfo/list
_______________________________________________
List mailing list
List@epicsol.org
http://epicsol.org/mailman/listinfo/list
