[sldev] Format of install.xml

[Brad Kittenbrink (Brad Linden)]

Rob Lanphier wrote:
> On 01/05/2009 07:31 PM, Ricky wrote:
>   
>> Thanks for the response!
>>
>> I think I will use the custom function approach.  It is fast to
>> implement (considering I already made the XPath string!) and I don't
>> yet understand enough Python... :P
>>
>> The downside is that my script is still dependent on something that
>> wouldn't normally be in the environment: The XMLStarlet package.
>>
>> I wonder... What would it take to rewrite the
>> serialization/deserialization functions so that the output XML was
>> better formed?
>>     
>
> LLSD is used in a LOT of places in the system, so it's pretty unlikely
> that we'd change the way that LLSD gets serialized to XML in general. 
> Using something other than LLSD for install.xml is something that might
> be more likely, but only marginally so, I think.
>
> I might be willing to help you out with this.  If you could have a
> command line utility that pulled the right out, how would it work?
>
> Rob
>   
If python hacking isn't an option, there are also perl and php LLSD 
serialization libraries which for some reason aren't being exported at 
the moment.  We should probably get on that...

You should really be able to work natively with LLSD in the language of 
your choice, as long as it isn't bash script. ;)

Anyways, you can probably get a lot of what you want by running 
install.py manually (it's what develop.py runs to fetch the library 
packages).  For example running the following will dump the information 
in install.xml for the boost package in a more human readable format (JSON):
> ./scripts/install.py --detail=boost

You can use it to list all packages, list all installed packages, and 
install and uninstall individual packages manually. Run 
./scripts/install.py --help for a full listing of what else this script 
can do.


-Brad