Re: Update mechanism for Raqcop.

David W Studeman wrote:

> Olaf Westrik wrote:
> 
>> On 2011-09-09 22:27, David W Studeman wrote:
>> 
>>> What makes the system know there is something newer than what you are
>>> running?
>> 
>> First IPCop will fetch the 'patch' file for the version it currently has
>> (1.9.20.xml).
>> That patch file containts either <latest/> or
>> <nextversion>1.9.21</nextversion>.
>> You are probably missing the modification in 1.9.20.xml to point to
>> 1.9.21
>> 
>> This is slightly different from the mechanism used in IPCop 1.4
>> 
>> 
>> Olaf
> 
> OK, now it makes sense. I did wonder why the system seemed to point to the
> current version. Now I know. It relies on that to tell when there is a
> nextversion available. I will try again with a 1.9.20 install to upgrade
> to the current svn.
> 
> Your idea to differentiate cobalt versus 486 in the updates was a good
> idea and will reduce confusion no matter where they are hosted. It's
> already complete and it didn't mess up the ability to compile as 486 since
> the Cobalts are still x86 without a bios. The latest ISO and Diff I
> uploaded as RC1 show the changes.
> 
> I'll study the 1.9.19 file from your patches to see how it points to
> 1.9.20.
> 
OK, that worked like a dream. I was able to dynamically download the update 
and appy it. I figured it had to be something simple and it was. Thanks 
Olaf!
-- 
Dave
http://www.raqcop.com


------------------------------------------------------------------------------
Malware Security Report: Protecting Your Business, Customers, and the 
Bottom Line. Protect your business and customers by understanding the 
threat from malware and how it can impact your online business. 
http://www.accelacomm.com/jaw/sfnl/114/51427462/