[sldev] Format of install.xml
kf6kjg at gmail.com
Tue Jan 6 19:26:25 PST 2009
Hmm.. I think I like the layout that install.py puts out. Still a little
hard to deal with grep-wise, but its layout and nesting structure looks like
the kind of structure I'd have liked the XML to be in.
I'm still mentally playing around with the idea of an XSL Transform for the
LLSD XML. If I do so, or something similar, it might make any /possible/,
however unlikely, conversion to a nicer format easier. As well as
Thanks for pointing me to install.py!
aka Cron Stardust
On Tue, Jan 6, 2009 at 10:03 AM, Brad Kittenbrink (Brad Linden) <
brad at lindenlab.com> wrote:
> 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?
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SLDev