On 19/11/2012, at 7:01 PM, fossil-m...@h-rd.org wrote: > >> From: Steve Bennett <steveb-sr3wrjstenvtt0ehb6f...@public.gmane.org> > >> I created a proof-of-concept branch (jimtcl) around this time last year that >> replaced TH1 >> with Jim Tcl. I also added support for writing "xfer" scripts in Jim Tcl. >> Richard was reluctant to incorporate this into the core fossil, I believe >> because of concerns >> over security. > >> Joe Mistachkin also added support full Tcl (which is in core, but must be >> enabled). >> Here the approach is to bridge via TH1 rather than replace TH1. > >> Cheers, > >> Steve > > Hi Steve, > > Thanks for the information. So is it be "better" to invoke tcl via TH1? Is > there any documentation on how to do that?
As it stands, this is the only option if you build from trunk. Joe, any docs? > And can I also invoke jimtcl, or only standard tcl? I'm asking because > jimtcl is already together with fossil, so no extra dependencies are involved. You need to build from the 'jimtcl' branch to do this. This version is somewhat old since I haven't been keeping it up to date. Cheers, Steve > > thanks, > > M. > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Embedded Systems Specialists - http://workware.net.au/ WorkWare Systems Pty Ltd W: www.workware.net.au P: +61 434 921 300 E: ste...@workware.net.au F: +61 7 3391 6002 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
