Forum OpenACS Development: TCLlib
Now, my proposal would be to take TCLlib and just add it as an OpenACS package like acs-tcl as no compiling is needed (to my knowledge, but might be wrong).
The benefit would be that the APM can decide whether TCLlib has to be included or not and you can easily install it without the need to install yet another package for AOLserver.
What do you think, am I missing something here?
here and there. I don't think we should add it to our cvs
though. Why not aolserver, all it's modules, postgresql, and oracle (if we can get it?).
But I agree, our track record for external software inclusion is not very encouraging, so maybe we should add this to the installer and the installation instructions.
Is there a way for the APM to not display packages for installation that have a TCL package require dependency ?
Talking about HTMLarea, I don't suppose we can retrieve this from a different place with the installer?
One more thing to note though. Everyone would have to keep their installations up to date on all the seperate packages and until we have the installers working, the installation would get even more complex.
This is in contrast to one person updating the ACS package and everyone just making an upgrade from repository or CVS, which is something you normally do on a regular basis anyway.
This said, I'd commit myself to update a TCLlib package every time a new release of TCLlib is available.
tclib takes advantage of many newer TCL additions and won't work reliably (at least when I checked it out over a year ago.)
- Install stock Tcllib, just like you install stock Tcl.
- "package require tcllib"
- As Jon G. brings up, understand what parts of Tcllib make not-true-under-AOLserver assumptions about the Tcl runtime environment, and avoid all use of those parts. (Probably add some sort of hook for AOLserver which disables those parts of Tcllib.)
If the last item above is too problematic, that is probably best solved either by adding additional support to AOLserver, or by tweaking the official version of Tcllib - not by forking the Tcllib code. As far as the additional AOLserver support, there has been some interesting discussion about exactly that on the AOLserver list recently, e.g., cheap cloning of Tcl interps.