RE: [PEAR-DEV] Template Proposal

At 02:01 PM 11/9/01 -0500, Chuck Hagenbuch wrote:

This entire discussion comes down to, essentially, two choices: a). PEAR == CPAN b). PEAR == Java standard class libraries Personally, the way to break it out seems to be not to merge them, but to have two layers: A core set of classes like DB, Log, Mail, etc, that have been adopted by pretty much everyone and aren't duplicated inside the core. They have consistent style, strict standards, and are actually kept under reasonable API control, etc. Then there's the general repository, which gets the benefit of all of the infrastructure - installer, whatever - and at least breaks everything out into its own namespace, but can hold 5 template engines, all the other DB layers, and anything someone wants to submit. Style is encouraged, but not mandatory, duplication is asked "is it really different?" but is fine, etc.

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?).

That's how _I_ think it should work. Admittedly, I skimmed/skipped a lot of this thread, but hey. :)

I think you're right. 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?? Peter. ---oOo--- sendcard - *The* PHP e-card solution http://www.sendcard.f2s.com/ ---oOo---