C. Scott Ananian wrote: > On Dec 5, 2007 10:28 PM, Chris Hager <[EMAIL PROTECTED]> wrote: > >> just finished a little coding session inspired by our olpc-austria >> meeting, and thought to share some news: >> >> 1. xo-get.py >> >> http://www.olpcaustria.org/mediawiki/index.php/Xo-get >> >> ... >> > If you want to continue working on this, > http://dev.laptop.org/ticket/4951 > tracks the design work we've done. > --scot Get te latest xo-get.py here: http://www.linuxuser.at/xo-get.txt
I can imagine my work on xo-get to provide a tool for quick installations / tryouts / de-installations of activities. Updates would be great, but the process seems a bit tricky. 1. At least we'd need a maintained .xo repository with version numbers, .xo-links, ... Is there something like this / is there a status? 2. Are / How are version-numbers saved on the xo? 3. To update only new files inside the zip would require a new kind of MANIFEST's with hashes, which I doubt will be here soon, since people stopped using manifests even in the demos :-) 4. Peer to peer updates would certainly be great! 5. The design ideas on http://wiki.laptop.org/go/XO_updater are certainly interesting, but that's like a biiig project :-) About self-updatings of applications: the wiki-page under #Design states: 'The problem is compounded by the fact that Bitfrost does not permit applications to update themselves in-place' I just tried it on a xo (build648), and it does work very well; if I understand you right (like a python script eg. a.py, writing a new version of a.py). Is that turned off on delivered laptops? - chris _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel