Excuse my bluntness: that sounds like a terrible idea. Tcl is huge compared to fossil, and certainly not installed everywhere by default. And for what benefit? To have a full-blown programming language built in? That of course isn't a benefit in itself. If an organization needs some sort of sophisticated processing attached to a hook, e.g. some verification on commits, let them call an external program, a shell script, a tcl script, whatever. Embedding an interpreter into Fossil itself, to run code called by the hook, seems like entirely the wrong approach.

_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to