Re: Re: [binarycloud-dev] Re: [PEAR-DEV] PEAR Package Requirementsand binarycloud

> Well I think the PEAR Installer is a good basis, but is not quite there > yet for applications. > > Stig, and a bunch of other PEAR developers (including myself) want to > make the PEAR Installer capable of handling applications (browse the > pear-dev archive for details). That's fine. I'm sure we'd be happy to help with the installer to get it up to snuff for binarycloud use after we complete Phing, and the pipeline tests. What I'm looking for is design and implementation details that could either slow us down (because of some major reorganization of code brought on by the installer) or stop us entirely (some as-yet-unknown problem). It's fine if the installer isn't quite there for sophisticated systems, we can help get it there if necessary. The most important things for us: -Easy setup + install -Dependency support that's smart (install + uninstall) -Package builds -Package checks -"Mirror" support for repositories eventually. Prefer a proxy or other system to the stupid CPAN "select-a-site" method. -Little overhead for "packagizing" code. (I see this in PEAR - not too much effort, which is good). -Documentation 'declaration'. Thanks for any responses, _alex