Automatic Script Updater

[Peter Zhou]

Seems I missed this important thread. Sorry for missing Jakob's hard
work! I agree that we can use the auto updater for the built-in
script. But why we need a public/private key validation when we are
using our own centralized server.

For the 3rd party script, I still insist that we should use
kde-app.org since the big change would be very expensive. We should
definetly make gns to support versioning and updating.

I undertand the usage of the version file now, seems good to me.


Sorry again for the delay. I was quite busy with my last
three-months-college-work.

On Saturday, October 17, 2009, Bart Cerneels  wrote:
> On Fri, Oct 16, 2009 at 15:52, Mark Kretschmann  wrote:
>> On Fri, Oct 16, 2009 at 3:36 PM, Leo Franchi  wrote:
>>> for now, why don't we do the script updater just for the scripts that
>>> we bundle with amarok. we'll do the hosting on kollide, one or two of
>>> us will have the private key, and we can see how it works in practice.
>>>
>>> if it's not as we want, we can always revert for 2.2.1 and try again
>>> for 2.2.2. But it's worth a shot, especially as the code is already
>>> written.
>>
>> Sounds good to me.
>>
>> --
>
> Agreed.
> And let's try to push for a solution for 3rd party scripts as well.
> I'm sure Jakobs excellent work will prove a good basis to build on.
>
> Bart
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>

-- 
Regards,
Peter Zhou
-------------------------------
http://www.peterzl.net/