Re: [binarycloud-dev] Re: [PEAR-DEV] PEAR Package Requirements and binarycloud

> pkg (package dependencies) > ext (extension dependencies) > php (PHP version dependencies) > prog (external program dependencies) > os (for example "windows-*" or "*-i386") > zend (Zend version dependencies) > > The package DTD also defines "ldlib", "rtlib", "websrv" and > "sapi", but > these are not implemented yet ("sapi" will most likely never be). OK, excellent. DTDs, the sort of dependency defs I was hoping for. >> -Build and preprocessing > > No preprocessing, only validation. The only build process involved is > in the "pear package" command that re-generates the package.xml file > with calculated md5 checksums, and makes a tarball. Ok, cool. > Just an idea so far: The installer has a "frontend" concept that lets > you plug different interfaces on top. We have a CLI, Gtk and web > interface today, adding an XML-RPC or SOAP frontend should not be too > difficult. Indeed. All work for the future, > Only package.xml is required. Ah, excellent. > Where can I learn about Phing? There will (soon) be much better documentation on phing, it's a subproject of binarycloud. Anyway - suffice it to say that it is an "architectural" copy of jakarta's ANT build tool http://jakarta.apache.org/ant/index.html with some additional features (including binarycloud-specific "tasks). Andi (andreas aderhold) started it, and it's now being lead by Jason Hines. It's progressing nicely, and is really the biggest hurdle to the binarycloud r2/RC1 release. After that we have some more work to do, but I think RC1 will be pretty close. The project will build easily then, so I expect we'll get a lot louder and ask for more contributors, and distribute tarballs with full docs early and often. The coolest thing about phing is the sophisticated XML buildfiles. The setup is similar in theory to the original ideas behind make (target dependencies, etc) but it's a lot cleaner and it's OO, and the makefiles aren't nasty scripts - they're XML. It's alsy very easy to build new "tasks" (like, for example, a ZendEncoder task). Phing is ridiculously cool, I'm using it in a project for a "pipeline" file processor, because it's a generalized file processing framework. The "build system" label does describe what it does well, but of course because it's PHP you can talk to a database during your build process :) You could write an article export to static HTML from a database "task" :) All, on bc-dev, message to come re: PEAR installer, etc. I think we may benefit from use of the pear infrastructure. Thanks for the response. _alex