On Sun, Jan 3, 2010 at 00:04, George Hunt georgejh...@gmail.com wrote:
Thanks,
the rpm solution works on at least builds 767, 802, and 1.5 FC11 backported
to XO1.0.
I'l go with that .
Good that's enough for you. For the sake of people who read the
archives, the portable way is to use
the portable way is to use jarabe.config.version for =0.84
and assume 0.82 if that's not present.
When running on an XO, how does one access 'jarabe.config.version' ?
It would be nice if the sugar version could be determined from within a
batch script. But I looked (in =0.84 builds) for a
On Sun, Jan 3, 2010 at 15:52, Mikus Grinbergs mi...@bga.com wrote:
the portable way is to use jarabe.config.version for =0.84
and assume 0.82 if that's not present.
When running on an XO, how does one access 'jarabe.config.version' ?
It would be nice if the sugar version could be determined
Should be something like this (don't have a XO around right now):
$ python -c from jarabe import config; print config.version
You can also grep the file jarabe/config.py.
Thanks - I didn't know about that file.
___
Devel mailing list
I've spent all morning googling to find the documentation of how to
determine which sugar build I'm running under -- without success.
If someone could point me in the right direction, I'd really appreciate it.
George
___
Devel mailing list
On Sat, Jan 2, 2010 at 9:09 PM, George Hunt georgejh...@gmail.com wrote:
I've spent all morning googling to find the documentation of how to
determine which sugar build I'm running under -- without success.
If someone could point me in the right direction, I'd really appreciate it.
You can go
Thanks,
the rpm solution works on at least builds 767, 802, and 1.5 FC11 backported
to XO1.0.
I'l go with that .
George
On Sat, Jan 2, 2010 at 5:37 PM, Peter Robinson pbrobin...@gmail.com wrote:
On Sat, Jan 2, 2010 at 9:09 PM, George Hunt georgejh...@gmail.com wrote:
I've spent all morning
