Matt Ingenthron wrote, On 07/23/08 07:46 AM: > Hi Jyri, > > Jyri Virkki wrote: >> I've been playing with phpmyadmin package again a bit and one >> unfortunate detail is that it's not possible to install it without >> installing all of MySQL5 on localhost, even if one wanted to use it >> to administer a remote MySQL instance. >> >> That's because phpMyAdmin requires PHP (SUNWphp524) and also the PHP >> MySQL extension (SUNWphp524-mysql). Now, SUNWphp524-mysql in turn >> needs the libraries to communicate with MySQL, but these are in >> SUNWmysql5 which is the full MySQL5 package. >> >> It'd be nice to have the MySQL libraries in a separate (hopefully >> small) package so clients which only need to communicate with a remote >> instance can depend on that package alone. >> > > I agree with this idea. > > However, having looked into this before (when deciding whether or not to > file an RFE :) ), it doesn't seem to be common in the upstream project > to ever package a "client" separate from the server. There are > "connectors" for things which don't depend upon the C libraries > associated with the server (namely Java, a native PHP version, .Net). > Other than that, all upstream distributions include the whole server. > > How do other distributions which bundle community server handle this? > I've not looked into this. Maybe someone on one of these lists knows.
I also agree - to the point I would insist :) Quite doable for IPS (did this myself for Java DB, which in SVR4, RPM etc form was already split like this, btw, but not picked up by the automagical translation into IPS (at least back then)) - a nightmare with all existing SVR4 packages... There is of course the packaging policy (Java ES requires adherence, might well receive a bigger following) on http://wikihome.sfbay.sun.com/wg-pkging/Wiki.jsp?page=InitialPolicies. While still a draft version 0.17 since Sep 2005, it does have quite sound policies and best practices, e.g in the "Modularity of Packages" section 1.1: Policy: Separation based on install location This would typically correspond to the "u" (user) and "r" (root) packages (think relocation, shared file systems, diskless clients, zones). Best Practics: Deliver logical groupings of related objects The current topic exactly (think client/server, download and install size etc). Best Practice: Linux: Use sub-packages where appropriate Typically found in Linux distros (rpm, deb) (refer to the Section's details and advice for more) -- Lars
