[Sugar-devel] updating from aslo

Tomeu Vizoso tomeu at sugarlabs.org
Thu Jul 16 13:13:56 EDT 2009


On Thu, Jul 16, 2009 at 18:23, David Farning<dfarning at sugarlabs.org> wrote:
> On Thu, Jul 16, 2009 at 10:09 AM, Daniel Drake<dsd at laptop.org> wrote:
>> On Wed, 2009-07-15 at 10:17 -0500, David Farning wrote:
>>> Attached is a very early prototype of a sugar updater which pulls from ASLO.
>>>
>>> It kind-of works on jhbuild;-/ To test, unzip and drop it into
>>> sugar-jhbuild/install/share/sugar/extensions/cpsection.
>>>
>>> run using 'install/share/sugar/extensions/cpsection/updater/model.py'
>>>
>>> Big Issues:
>>> The GUI interface is reporting a network error.
>>
>> I personally feel that this kind of approach is not a great idea, but I
>> suppose it depends who your target users are.
>
> A possible answer would be to abstract ALSOParse.py and microformat.py
> as back ends for Sugar-Update-Control (SUC).
>
> SUC could either fall back from ASLO to microformat or be configured
> to connect to either ASLO or microformat by default.

Would be possible to autodetect the format that the server understands?

> A third alternative would be to add a local-server backend.  It would
> be pretty straight forward to write a script to poll ASLO for
> available updates, create a text file of available update, and
> download the updates to a directory.  This data could then be moved to
> individual deployments as needed.
>
> SUC could then update individual machines from a local server using
> data created above.
>
> I'll start working on abstracting out the backends today.

Great, I hope to find time tomorrow to give it a first look.

Regards,

Tomeu

> david
>
>> This type of setup seems inappropriate for low-bandwidth/high-latency
>> OLPC-style deployments, since it seems to rely on the internet. Unless
>> you're suggesting that people run the updates website on the school
>> server, in which case xs-activity-server would need to be reworked into
>> that, or an alternative solution developed which does not require
>> deployers doing too much setup.
>>
>> The current updater has some nice properties in that the microformat is
>> simple, the surrounding infrastructure is in place for deployments (use
>> xs-activity-server, or maintain a .html file), and that at least with
>> this patch it will operate very well even without internet access:
>> http://dev.laptop.org/ticket/9259
>>
>> Daniel
>>
>>
>>
>
>
>
> --
> David Farning
> Sugar Labs
> www.sugarlabs.org
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


More information about the Sugar-devel mailing list