Re: changes to package.xml 2.0

Alan Knowles wrote:

This obsoletes the need for --alldeps and --onlyreqdeps. I've also written code for two simple xml-rpc functions that will allow complete dependency resolution BEFORE downloading any code. I'm working on the extremely complicated client-side algorithm for checking all deps (you should see the UML diagram I wrote up to help me out :).

He, who walks where others fear to tread :) -

Maybe someday I can code tall buildings in a single bound.

If you are going to produce an example for the package.xml - it's proably worth using <group name="optional" hint="These are optional packages"> .... Just so people moving from old package.xml understand how to do it..

That is exactly how the automatic converter from 1.0 to 2.0 will work, it will create 2 groups, one from required deps and the other from optional deps, with a <!-- comment --> explaining a bit on what can be done. I just haven't written it yet :). I figure people can learn more by taking the existing package.xml's from their packages and converting them using the converter, as the analogies will be obvious. Greg