Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.9.5

Request #10391 Split developer-related tools into a separate package from the installer
Submitted: 2007-03-15 10:05 UTC Modified: 2007-10-28 01:18 UTC
From: cellog Assigned: cellog
Status: Closed Package: PEAR (version CVS)
PHP Version: Irrelevant OS: n/a
Roadmaps: (Not assigned)    
Subscription  


 [2007-03-15 10:05 UTC] cellog (Greg Beaver)
Description: ------------ In order to streamline the installer and to simplify both bug tracking and feature addition, the developer tools for - packaging - managing package.xml etc. should be split off into a separate package that can be installed via an install group.

Comments

 [2007-03-31 06:17 UTC] dufuz (Helgi ├×ormar)
What I suggest is that each PEAR package (not as in the whole repo, just PEAR :P) can install "commands", so if I only have the installer and I do pear package then I get "this command is unavailable" or similar and when I install pear_development_packaging and do pear package then everything works smoothly. This could be stored in the sqlite db with descriptions and what not and just cached into an array file for the console to use so we won't be hammering the db all the time when we issue a pear help or similar ;-) Of course we could just have the standard ones hardcoded but then one thinks, what about this. we have PEAR_Base, has the sqlite db perhaps and just the basic things, the pear installer and development packages extend that and then we maybe could provide people with a way to use only the dev parts with out even having the installer :-) Might sound odd since most developers would like to verify their tarball by installing it but hey why not be flexible enough if it is fully possible
 [2007-10-28 01:18 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.