edh01 - This may be a question for PSARC and precendence. I notice this installs in /usr/squid. I thought we wanted functional names in the path? Is /usr/squid the right place in Solaris?
edh02 - Where do the version tags described in section 2.2 appear? They don't appear as part of the command names as listed in the spec. How do I query them? edh03 - In section 2.3 when you say the "modules" are these modules supplied by squid or by the user? I assume they are the modules described in section 3.0 Are all of them compiled in all the time? If not how do you choose? edh04 - Since squid needs to be recompiled each time does that mean you're delivering source to the end user? edh05 - Who winds up calling/using all the things in /usr/quide/libexec? Why aren't they in /usr/squid/bin? -edh Jyri Virkki wrote: > I am sponsoring Fast Track WSARC/2007/554 "Deliver Squid into > OpenSolaris" for Rahul Gopinathan and the OpenSolaris Web Stack > community. Timer is set to 10/04/2007. > > Functional spec is in the materials directory: > http://sac.eng/WSARC/2007/554/materials/squid.txt > > Case materials also available on opensolaris.org (though not quite > yet, it takes a bit for them to propagate): > http://www.opensolaris.org/os/community/arc/caselog/2007/554/ > > > > Notes: > > This is the first OpenSolaris and the first "Exposure: open" case > through WSARC (see wsarc-EXT at sun.com). > > This is a new component (Squid is not yet in OpenSolaris). WSARC > traditionally has done full reviews for new components. This follows > the path of e.g. PHP (PSARC/2007/168) which also ran as a Fast Track. > > This case is relatively simple and uncontroversial compared to some of > the other web stack cases such as PHP (approved PSARC/2007/168) and > Apache since Squid lacks the complexities of those cases. Squid does > not have support for external modules and no interface breakage is > expected in minor versions. > > >
