I don't know where this (as well as many of Sugar's APIs) are documented. It would be best to look at the original PHP code as well as the clients' intent:
- http://git.sugarlabs.org/slo-activities/mainline/blobs/master/site/app/webroot/services/update-aslo.php - http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/sugarlabs_activities/kspost.60.nochroot.aslo.sh - https://github.com/sugarlabs/sugar/blob/master/src/jarabe/model/update/aslo.py There are ways to build XO builds and update Sugar activities without ASLO (although no automated one for apps installed to a user's home directory). A bigger decision might be to eliminate getting Activities through this API. On Thu, Jul 14, 2016 at 2:48 PM, Dave Crossland <d...@lab6.com> wrote: > > On 14 July 2016 at 13:13, Samuel Greenfeld <sam...@greenfeld.org> wrote: > >> The build utilities for XO laptops hook into ASLO to download >> applications. >> > Cool! > >> Some sort of backward compatible API should be made for that. >> > Sure. Where is the API documented? >
_______________________________________________ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
