Does anyone mind if I split the installation process in 2 stages? make install -> module + binary libraries + init.tcl + Tcl commands
make install-packages -> the whole content of rivet/packages is copied onto the installation target and the pkgIndex.tcl file regenerated pros: Pure Tcl packages can be shipped, installed and managed separately. The core module should be functional whether the packages are installed or not. my goal is to produce a module linked with Tcl8.6 to be shipped with Debian/Ubuntu to work as a replacement for the standard 8.5 based module without packaging the Tcl/Itcl stuff for both thoughts? -- -- Massimo Manghi P.S. btw, the packages directory deserves some clean-up of unused stuff. --------------------------------------------------------------------- To unsubscribe, e-mail: rivet-dev-unsubscr...@tcl.apache.org For additional commands, e-mail: rivet-dev-h...@tcl.apache.org
