Re: Re: subpackages and bundles
| From: | Tomas V.V.Cox | Date: | Fri, 04 Jun 2004 09:10:19 +0000 |
| Subject: | Re: Re: subpackages and bundles | ||
| References: | 1 2 3 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-367@lists.php.net to get a copy of this message | ||
Greg Beaver wrote:
Tomas V.V.Cox wrote:Greg Beaver wrote:
People are more than accustomed to seeing "Typical" "Minimal" and "Custom" in windows installations. This is exactly the same thing.[..]
Yes sorry, I'm feeling as brick wall ;). But see, I'm accustomed to Linux installations. Just an example: $ urpmi foo-devel bar1 bar2 foo foo-devel depends on these packages. Do you like to install them? (Y/n) The same goes for any remote package installer like apt, yum or up2date. Easy and nice, no dumb wizards, no need to know anything, just install and use. RPM never needed subpackages and Linux distributions are there, with thounsand of packages and tricky deps. IMHO subpackages are throwing more complexity than real benefits and because I'm just lazy, adore simplicity. This is my main argument, let's cut down this discussion :-) BTW I find the "parent" param good addition for maintaning installations clean of garbage packages.Haven't yet seen a real need for subpackages, please prove me the contrary :)Why do I feel like I'm talking to a brick wall :).
Let's start compiling a list of stuff that could be usefull to be avaible for pre/post scripts: - Access to the $package array (the package.xml converted in an array) - Access to the config - Access to the registry - Access to the file operation methods (PEAR/Installer.php) - Access to downloader - Access to frontend I'm not sure about the installer asking the user where to install the db schema or things related to database, in many cases you need to create users or databases before, start the backend, many times there are errors and you need to reexcute the action, etc. I'd let this point to the application itself. Maybe we could provide an importer/exporter class. We could just take horde, phpnuke and phpbb and try to pack them to see what would they need :) Tomas V.V.CoxThat's the easy part, just a pre and post call to a php script, AFAIR that was even supported (not handled) by the package.xml parser. If we want to be kind we could provide some functions to common tasks.pre and post call is not nearly enough configurability, the scripts need to have full access to configuration, and other information the installer has access to, otherwise you might as well write another installer from scratch in the scripts.