RE: [PEAR-DEV] Template Proposal

Quoting Peter Bowyer <reywob@f2s.com>: > This is what I think we need. How about pear.php.net for the core and > repository.php.net (or a more snappy name if you can think of one!) for all > the other stuff? This leaves PEAR to concentrate on the core without > being cluttered, while providing an alternative to Hotscripts.com for > _decent_ PHP classes (and maybe applications?). It can all be PEAR. PEAR Core, PEAR Repository. Or the PEAR Framework and the PEAR class collection. Nomenclature is, contrary to the volume of discussion spent on it, just not that important. > One drawback of this (which applies also when PEAR isn't distributed with > PHP any more) is that some hosts won't install the packages from the > general repository people want, and so the contents lose some of their > usefulness - unless you're thinking of them being installed into the > developer's directory and not the PEAR folder?? The web/command-line/php-gtk installers should be able to install all of the packages - core and otherwise - into someplace where you can include them, no matter the hosting environment. -chuck -- Charles Hagenbuch, <chuck@horde.org> "What was and what may be, lie, like children whose faces we cannot see, in the arms of silence. All we ever have is here, now." - Ursula K. Le Guin