Hi Steve, See my comments in line.
Thanks. Steven M. Christensen ??: > As with gdbm and lua recently, if clisp is in SFW, some programs will > find it and try to use it and thus introduce a dependency on it. Swig > has the configure options > > --without-clisp Disable CLISP > --with-clisp=path Set location of CLISP executable (clisp) > > for example. When you do your full SFW test build with clisp > included, check to see what swig does with clisp. If it uses it, > someone will have to add the clisp package dependency into swig or fix > swig so it does not use clisp. The configure script for swig package in sfwnv gate don't specify either of above two options. And according to the output of "make -f Makefile.sfw install", the building process did not use clisp. So I think there is no dependence. > There may be other packages that find clisp as well. I have searched the source tree of "usr/src" by "grep -i clisp * -r", and did found any other package which contains "clisp" keyword. So it seams safe to integrate clisp. > > Steve C. -Charles He
