This hasn't been our experience so far. And I'd really like to see PEAR take
the step to components not in PEAR CVS - I'd like to provide other Horde
components as PEAR packages this way eventually, and since there's interest,
this one seems like a good one to start with.
As I said, PEAR developers are welcome to get Horde CVS accounts or to just
send us patches to work on this.
Not that I wouldnt love a Horde acount :), but one of the benifits of using pear's cvs, is that when there is something 'obviously wrong' with a pear package - eg. A bug... anyone with a pear account can fix it - by commiting it. (and get shouted at if they break something :)..
This has happened a number of times here where a package produced warnings under E_ALL or somebody has commited Cases Sensitivity patches to my packages. It makes life alot easier for package mainterers - if someone suggets an extra method to their package (and the owner likes it), then if the proposer has a pear account, they can go ahead and commit it, saving the maintener some time..
It also makes browsing the source code easier to find (as that is often the best way to review a package before using it)..
Especially as I can see alot of uses for a VFS class - not only to replace the mess that is in phpmole at the moment :)
So personally I would prefer all packages (where possible) to be in the pear CVS.
Regards
Alan
-chuck
--
Charles Hagenbuch, <chuck@horde.org>
"After a few minutes the most aromatic and nice smelling Italian coffee will come out of the exhaustpipe." - Our stove-top espresso pot