RE: [PEAR-DEV] PEAR Package Requirements and binarycloud

Dependencies are registered in the package.xml as follows The example comes from Math_Complex (http://cvs.php.net/co.php/pear/Math_Complex/package.xml?r=1.2) <deps> <dep type="pkg" rel="ge" version="1.0">Math_TrigOp</dep> </deps> There are several "type", i don't know them by heart nor can i find them in the doc... ge is greater than but that's all i remember. Preprocessing is done by lauching pear package-validate, which reads the package.xml and validates it. Building is done via pear package, it builds a tar/gz file. YOu can provide this file and users just have to do a pear install xyz.tgz remote install, the easiest way is to provide a taz/gz and ask the user to do download and install it. This is but a quick'n'dirty overview. Somebody with more kowledge (stig ? ;)) should be able to help better. Arnaud. > hi guys, > > I think we'd like to use the PEAR package system for > binarycloud. Certainly > for compatibility and "resource sharing" it seems like the best path. > > However, I do not have a sophisticated understanding of the > installer, and I > wonder if anyone would be willing to respond to this message > with a fairly > detailed explanation of the workings and requirements of the > PEAR installer > + package xml. > > Specifically: > -Package dependencies > -Build and preprocessing > -Remote installs > -Required files "in" a package (like package.xml, others?) > > This is for my benefit, as well as the binarycloud-dev list's benefit. > > If the pear package system fits what we're doing (as I hope > it does) we'll > do what's necessary immediately to turn binarycloud into a > PEAR package > hierarchy that's installable. > > Then Phing (our build system) can take care of configuring > and building > those packages. > > Thanks, > > _alex > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >