On Sat, Apr 5, 2008 at 3:01 AM, Jyri Virkki <Jyri.Virkki at sun.com> wrote: > > Peter Tribble wrote: > > > > However, it appears that the supplied apache httpd.conf simply > > Includes conf.d/*.conf so that everything installed is enabled by > > default. I'm not at all sure that's a good idea, but that's a more > > general problem and isn't a specific problem with phpMyAdmin. > > That is an excellent point, to which the answer is that OpenSolaris is > right in the middle of a transition period and the optimal answer is > different on either side.. > > If this package goes into the traditional Nevada-based distribution > (one DVD with all packages and they all get installed at once), > clearly the phpMyAdmin package cannot automatically enable itself > since the reality is that most people don't want it enabled on their > apache server. > > On the other hand, when installing from a package repository > (Indiana-style) the best answer is for phpMyAdmin to drop it's config > into conf.d when the package is installed. Since this is not a default > package on the LiveCD, it will only ever get installed by those users > who specifically want to use phpMyAdmin, so having it deliver live > configuration is the right answer for them.
Not entirely. As soon as you put zones into the mix the above argument fails. Assuming sparse root zones, he same software is installed into each zone - only some of which may actually want to enable a particular feature. Also - and I don't know whether the way I build systems is representative or not - when I build systems (and this isn't going to change if the delivery mechanism changes) that might be used for consolidation or virtualisation, I tend to install everything that might be useful up front and then enable features on each system or zone as required. (Especially as zones migrate between systems - so you really do want the same reasonably complete software stack on each system.) -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
