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. There may be other packages that find clisp as well. Steve C. Jim Walker wrote: > zheng he - Sun Microsystems - Beijing China wrote: >> Jim Walker ??: >>> You need to decide if you want to provide the object files. >>> If you do then you would answer yes to each of these questions: >>> >>> 3.1.2 Share and Sharable >>> Does the module include any components that are used or shared by >>> other projects? >>> [ ] Yes >>> [*] No >>> >>> If yes are these components packaged to be shared with the other FOSS? >>> [ ] Yes >>> [ ] No - ARC review required >>> [*] N/A >>> >> Does "Yes" for this two question conflict with answer "There is no Sun >> proprietary code which uses clisp" for question >> >> *What is the abstraction layer between the GPL/LGPL code and Sun's >> code? >> > > No. There is still no Sun code using clisp. > > Cheers, > Jim > _______________________________________________ > sfwnv-discuss mailing list > sfwnv-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss
