On Sat, 14 Jun 2008 21:37:00 +0100 Peter Tribble <peter.tribble at gmail.com> wrote:
> On Fri, Jun 13, 2008 at 10:55 AM, Nick Kew <Nicholas.Kew at sun.com> > wrote: > > We've been discussing internally Sun's plans for our work > > with the Apache web server (HTTPD and APR) in the webstack. > ... > > As a first topic, here's the executive summary overview > > of our broad goals in this work as I see them. > > In no particular order: > > - Improve the webstack/coolstack bundles in OpenSolaris. > > - Contribute to the broader community, including upstream > > development at apache.org. > > - Seek ways to make apache-on-solaris a killer platform, > > and a sellingpoint for solaris over other platforms. > > In my other post, I blathered about no using the Sun-supplied > components. Thanks for your comments, in both posts. > It's a heck of a lot easier for me to unpack/configure/build/install > and make work for source than it is to use what's on the disk. That of course is your choice. The feedback we get at apache suggests that more people use downstream packages (e.g. linux .deb/.rpm, windows .msi) than build from source. It is for those users we should provide packages. If we're not doing as good a job as the competition, it would be good to know. > But this is what would help: > > Actually installing a component is trivial. That's the easy part. > It's integrating a number of components together into a working > complex system to supply a service that's hard. > > So I might want to set up an svn server (using apache); or get > a wiki running; or set up a bugzilla instance. It's those solutions > that are important. > > Forget the individual components, having a trivial way to get such > complex integrated systems running is where you could really make > a difference. And I don't means HOWTOs or docs or blog entries, but > (shudder) wizards that install and configure everything for you. Interesting thought. I guess this could in principle become an extension to the existing packaging: add packages for "foo wizard" that depend on "foo" basic package and its prerequisites. So for example, add a svnwizard package that pulls in svn/apache/etc and configures it all for you. This is going more than a little outside my field: my customary reaction to any "wizard" is to curse and swear at it not allowing the options I want. But I'll bear it in mind, and maybe others can follow it up better. -- Nick Kew
