Hi Andrew, could you do the effort again (taking out the acs-tcl package) and clean it up so that:
- All procedures that are required by acs-tcl that are independent of OpenACS but somehow made it into a different directory, are moved into acs-tcl.
- All procedures in acs-tcl that rely on code in OpenACS are moved to acs-kernel.
If I'm not mistaken this should enable us to maintain an acs-tcl package that is clean of OpenACS dependend code and can be reused everywhere else. We might even upload all these enhancements to the AOLserver CVS .
I'd assume if we want to make a policy out of this, we would have to TIP this, therefore it would be nice to get some feeling if people agree to be doing this. I for myself am sold to the idea and it makes a lot of sense to me (as I was always wondering why we have acs-kernel and acs-tcl and this differentiation posted by Andrew makes utter sense and should be published in guidelines).