Re: Update mechanism for Raqcop.

On 2011-09-03 09:23, David W Studeman wrote:
>   Since I have Raqcop for the Cobalt crowd, I now have my own public gpg key
> in the Raqcop builds as of now and then sign them, this will be in the next
> build be it rc2 or the actual 2.0 release depending on IPCop itself as far
> as the public being able to use it. This means that it will require a clean
> install the first time and then can be upgraded after that with little
> effort so anyone (all three people?) using Raqcop-2.0rc1 will not be able to
> upgrade to rc2 or 2.0 via the web gui. So far I can install after uploading
> via the web gui. I also have the cgi script and the functions perl library
> pointed to an update and a patch folder on my site.
>
> In the updates folder, just the gpg signed update and the release notes
> exist and in the patches folder, a 1.9.x.xml file exists. Am I missing
> anything? My site does not like any of the methods of retrieving files other
> than using a web browser. It throws an "ERROR 406: Not Acceptable" message.
> I am trying to get Brian Ridgeway to take a look since he hosts it and set
> it up, I have enough priviledges to get where I am so far but it is Brian's
> domain and hosting. Meanwhile I want to know if I have missed anything. It
> would appear that IPCop looks for three files in two directories.

Everything is in general-functions.pl and updates.cgi.

Alternatively we could host the cobalt updates on SF, but that would 
require renaming the update to something like 
ipcop-<version>-update.cobalt.tgz.gpg

That could prove to be an interesting exercise...


Olaf

------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev