rpm vs xo & activity updates

[Daniel Drake]

On Tue, 2009-06-23 at 21:52 +0200, Mathieu Bridon (bochecha) wrote:
> > - rpm-based packages cannot be updated with Sugar's updater utility,
> > which is the primary way for updating activities right now. There is no
> > upgrade path for activities installed by rpms (without updating the
> > whole OS, which is another open question)
> 
> You can update only one activity with:
> # yum update sugar-<activity>

This is not a suitable interface for our users.
We need something easier, or something automatic.
And any work in this direction would probably be bolting onto the sugar
activity updater, making it really confusing with 2 backends or
something, and sort-of calls out for a rethink of the system as a whole.
Speaking of which...

> I proposed the following some times ago [1], but no one responded. I
> would have loved for someone actually knowledgeable (i.e. not some
> random guy like me throwing out ideas he can't even implement) to
> explain how this would be a terribly bad idea :)

snip..
I love these ideas. I would even go as far as to remove .xo support
altogether as there are a number of flaws in that format now that sugar
is hugely increasing in scope.

Daniel