Re: Could some kind soul review these patches please.

John Donagher wrote: > > My issues with CPAN are mostly usability issues. The initial setup (i.e. the first time you run > it) is somewhat lengthy and annoying. I have to use it so rarely that it always takes me a few > minutes to remember all the commands or the exact syntax thereof. Whatever kind of PHPCPAN system we > build, I think we have to take steps to ensure that it doesn't require significant training on > the part of the installer. A command line interface (make config) is necessary, but perhaps an > optional CURSES interface (make menuconfig) would make things easier for people who only install a > new module once a month, or every couple of months. > > Since we may, from my understanding, keep the PHP C extensions seperate from PEAR (which kind > of makes sense, and yet kind of doesn't), this interface will be used less by an installer than > CPAN would be. Will an installer be able to download the source to modules, or only a prebuilt > binary for use with dl()? Assuming he can download the source, I think we'd eliminate the > negative installer experience by weaving this process tightly into the build process. Could this be > done with our current ./configure? I'm not sure. PEAR will have C extensions. There is a lot of confusion of what PEAR is/will be, but the basic idea is the same as for CPAN. But we are going to make it easier to use, and hopefully avoid the worst duplicates of functionality that CPAN has. - Stig