[Sugar-devel] More concrete design for easily installable device extensions?

[David Farning]

On Mon, May 11, 2009 at 10:47 AM, Gabriel Eirea <geirea at gmail.com> wrote:
> Excuse me if I jump into this discussion. There is a problem here in
> Uruguay related to this issue. Given the security system implemented
> by Ceibal, users don't have root access. This makes it very difficult
> to include changes in Sugar, like the clock described in the parent
> post.
>
> Would it be possible to devise an extension architecture that would
> allow to install extensions without root access? This would be very
> helpful for us.

A more feasible solution might to focus on rainbow, or another
security solution, and give users root when they upgrade.

Kludge on top of kludge, while easy to write, quickly becomes
difficult and expensive to maintain.

The community development process is very very good at making standard
collaborative platforms.  Modifications, customizations, and value
added features are best handled by ISV.

david

> Thank you,
>
> Gabriel
>
>> 2009/5/11 Michael Stone <michael at laptop.org>:
>>> Simon Schampijer wrote:
>>>
>>>> a) this could be a good moment to get the infrastructure on
>>>> activities.sugarlabs.org for device extensions up - or at least to think
>>>> about how we can realize that...
>>>
>>> Simon,
>>>
>>> Could you please offer a more concrete description of the use cases and design
>>> that you have in mind so that those who wish to may reflect on its interaction
>>> with Sugar's existing (0.84) and previous (0.82) security models and
>>> situations?
>>>
>>> Thanks,
>>>
>>> Michael
>>> _______________________________________________
>>> Sugar-devel mailing list
>>> Sugar-devel at lists.sugarlabs.org
>>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>>
>>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>