Amanda Does FastCGI has compatibility issues between versions like apache or php. If so, then it is understandable to keep it under /usr/fastcgi. otherwise, I am wondering why not place it under /usr
Please note that most linux distributions does ship components under /usr. Now, upstack components when they need to build they mostly look under /usr. So, we should try our best to keep the components under /usr and headers under /usr/include so that other components are able to build - just like in linux - without much modifications to their build system. Unfortunately, within web stack - we have lot of components that are placed under /usr/<component-name> rather than under /usr - sriram Amanda Waite wrote: > Hi again, > > Attached is a revised draft of the FastCGI ARC case. I've added the > man pages for the executable and the API calls. I've also included > details of the master man page. There are no changes other than that. > > Feel free to comment or ask questions. I'd rather you guys picked out > the holes in this than have the ARC do it. > > I have only one outstanding question, do I include static libraries > for something like FastCGI? I know that the general policy is not to, > but there are a lot of applications out there that build with the > FastCGI libraries and they may not all like being unable to find the > static libs. It's easy to say "fix the app that's linking the > libraries" but it's not always possible. > > Cheers > > Amanda > > > ------------------------------------------------------------------------ > > _______________________________________________ > > > webstack-discuss mailing list > webstack-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/webstack-discuss
