[Sugar-devel] Activity packaging

Jon Nettleton jon.nettleton at gmail.com
Sun Aug 8 10:18:51 EDT 2010

> But the one of core ideas to not use only regular packaging systems
> (via PackageKit or directly) is having this, natural and desired,
> scenario for sugar ecosystem:
> * there is an activity,
> * several users might decide to experiment w/ this activity
>  (i.e. change its code) and share this results
> * third user wants to try all these experiments (including pristine
>  activity)
> This scenario is pretty undoable (by design) in native packaging systems
> but 0install is designed to support scenarios like that (all
> activity implementation are stored in separate directories in user's
> home and can be launched in any time and even at the same time).

This doesn't sound like a package management system scenario.  Really
this sounds like a revision control system is needed.  Wouldn't it
make the most sense to integrate bzr or git into sugar to handle code
sharing like this?  Then you could continue to have all the Activities
in a single directory with multiple branches to can be switched
between on the fly through a sugar interface.


More information about the Devel mailing list