Hi,
Just for perspective. The approach which I have taken is to install the
activities from ASLO in the library. Any XO connected to the library can
select an activity to be downloaded and installed. If storage becomes a
problem, an unused activity can be deleted locally.
Tony
On 09/06/2012
On Wed, Sep 5, 2012 at 9:09 PM, Gonzalo Odiard wrote:
> Maybe we can prepare a Feature for the next cycle.
> Also, we are shipping a old updater, not integrated with the changes done in
> sugar
> (sugar was changed to support different backends, as ASLO and OLPC,
> but our code does not implement
