David.Comay at Sun.COM wrote: >>>> 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. Thanks for this bit of clarification. I guess that has all sorts of implications. Current web component packaging is designed so that, for example, httpd 2.2 can continue to be delivered alongside future httpd 2.4. If the right thing is supposed to happen whenever the user specifies only the rightmost component (e.g., pkg install plugin-dtrace), then perhaps plugins have to be qualified not just with "plugin" but also with the MAJ.MIN version of the version of the container they are built for. (I'm guessing that I took that too seriously :) )
A couple of more random comments: web/amp consider web/server/amp for 5 seconds since this is purely server side; seems like it would be interesting to see web/server/* web/server/lighttpd I guess the future-proofing "14" in the existing SUNWlighttpd14 package name was intentionally dropped? database/mysql-5/* With the benefit of hindsight we now now that this 5 means "5.0" and is distinct from "5.1". It might just be helpful to use database/mysql-50/* Stuff I think we all (here) agree needs to be changed: web/library/apache/apr-13/* change to library/apr-13/* web/library/apache/apr-util-13/* change to library/apr-util-13/* web/server/apache-22/plugin/plugin-fastcgi change to plugin-fcgid web/server/apache-22/plugin/plugin-html-plugin change to plugin-proxy-html web/server/apache-22/plugin/plugin-tomcat change to plugin-jk Thanks!
