No matter how we do it I believe we really need it. I personally prefer the first solution because I can directly see which packages are customized since I only work in a directory.
Two additional thoughts:
1. the naming should be a parameter
2. the customization should be configurable on subsite level. Maybe we provide a default word like 'custom'.
This would allow a single installation of OpenACS to serve different customized versions. The request processor can check for each subsite whether customized pages exist and serve them.
Another extension to 2. would be to lookup customized files automatically. Thus if I have a subsite foo and a subsite bar then the request processor checks for *-foo.tcl and *-bar.tcl file to serve.
I agree to Dave that we need to have customization on instance level. Thou I believe that on subsite instance level is enough.
