>>> a. SUNWapr13 web/library/apache/apr-13 >>> This is a general purpose portable OSS library like glib or others. >>> Should it really go under "web"? (obviously a web server depends on it) >>> >> >> It's the only thing under web/library, and the meaning of "apache" leaves >> room >> for doubt (httpd or asf?). +1 to drop the web. >> > > Potentially the FastCGI programming library could go under /web/library (it > is currently /library/fcgi).
It does seem like web/library/fastcgi makes more sense. >>> b. SUNWspawn-fcgi web/fastcgi/spawn-fcgi >>> >>> Shouldn't this go under web/server? >>> >> >> Disagree, unless the whole of fastcgi goes there. >> > > Shrug. The whole of fastcgi right now seems to be > > mod_fcgid > FastCGI programming library > spawn-fcgi > > I guess web/fastcgi for the latter two works for me. A "fastcgi" category > isn't going be so helpful long-term though since Perl language bindings would > be expected to be named like other Perl modules, and the same for Python, > Ruby, etc. (Just as httpd users would expect to be able to find extra modules > under a specific hierarchy. I'm open to suggestions here. >>> c. SUNWphp52-mysql web/php-52/extension/php-mysql >>> >>> Why does "php-" have to be repeated >>> >> >> Um, the meaning is clear. Drop the second one and there's potential for >> confusion. >> > > But they'd see "mysql" under php-52/extension. IPS will match starting with the rightmost component so "pkg install mysql" would match the PHP extention rather than an expected MySQL package.
