[sugar] Installing new non-core designated activities

Gary C Martin gary at garycmartin.com
Thu Mar 6 08:42:08 EST 2008


Hi List,

I'm sure the sudden, poorly communicated, policy change regarding what  
is and isn't a default installed activity anymore (in build 696 and  
up) has given many developers/testers a very unpleasant surprise. What  
is the official method to re-installing these activities if we want to  
continue to test and work with the newer builds right now?

And before any one say, "use browse, visit the activity page and click  
the .xo bundles you want", that's not an option for the majority of  
activities that just got dropped, as their developers probably didn't  
realise they were about to fall out the loop, there are no browser  
installable .xo files for most.

The XO get, gui just hangs, so no luck there, and xoget command line  
only seems to work from the Terminal activity (which was dropped) as  
the hidden command prompt doesn't have the right environment (DBus  
complains about accessing X for some reason).

Only other thing seems to check out the source on another machine  
using GIT, building your own .xo bundles, and hosting them somewhere  
browse can get to... Or are we all meant to start building our own  
auto package installer custom USB sticks?

Hopefully I'm just missing something really obvious here.

Thanks for any pointers,
Gary



More information about the Sugar mailing list