Easiest way to run the latest activities

[Bert Freudenberg]

Am 11.07.2008 um 12:20 schrieb Simon Schampijer:

> Morgan Collett wrote:
>> On Thu, Jul 10, 2008 at 11:35, Bert Freudenberg  
>> <bert at freudenbergs.de> wrote:
>>> Am 10.07.2008 um 10:44 schrieb Morgan Collett:
>>>
>>>> On Wed, Jul 9, 2008 at 21:31, Bert Freudenberg <bert at freudenbergs.de 
>>>> >
>>>> wrote:
>>>>> Am 09.07.2008 um 20:07 schrieb Sayamindu Dasgupta:
>>>>>
>>>>>> On Wed, Jul 9, 2008 at 11:12 PM, Daniel Drake <dsd at laptop.org>  
>>>>>> wrote:
>>>>>>> On Wed, 2008-07-09 at 23:11 +0530, Sayamindu Dasgupta wrote:
>>>>>>>> The easiest way, perhaps, to run the bleeding edge version of
>>>>>>>> Sugar on
>>>>>>>> an XO is to run the latest joyride. Is there a similar way to  
>>>>>>>> run
>>>>>>>> the
>>>>>>>> latest activities on an XO ?
>>>>>>> I use:
>>>>>>> http://dev.laptop.org/~bert/joyride-activities.py
>>>>>>>
>>>>>>> see http://wiki.laptop.org/go/Bert%27s_script
>>>>>>>
>>>>>> Hmm.. for some activities
>>>>>> http://dev.laptop.org/~erikos/sucrose-activities.py seem to  
>>>>>> provide
>>>>>> more recent stuff.
>>>>> Really? That would mean the latest Sugar release is not in  
>>>>> Joyride,
>>>>> which would be a problem.
>>>> Bert's joyride-activities script seems to pull from
>>>> http://xs-dev.laptop.org/~cscott/repos/joyride/, which is very  
>>>> out of
>>>> date. For example, it has Chat-37 as the latest, but Chat-42 has  
>>>> been
>>>> released.
>>>>
>>>> How do we get activity updates in there?
>>>
>>> By the normal Joyride procedure (put the .xo into your ~/ 
>>> public_rpms):
>>>
>>> http://wiki.laptop.org/go/Build_system#Instructions_for_Use
>> Ah, since the activities were removed from the build images I stopped
>> doing that. I'll do that again.
>> Morgan
>
> Yeah until we have another way to update the activities I think the  
> best is to update by the normal joyride procedure. To get a full  
> list of the latest activities and not only the sucrose ones.
>
> I will do the ones I maintain now as well and encourage you to do so  
> as well unless someone has a better idea.
>
> Best,
>   Simon


Heh, I just kept doing as part of my regular release procedure ;)

- Bert -