Skip site navigation (1) Skip section navigation (2)

Re: RFC: Update wizard

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de>
Cc: "pgadmin-hackers" <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: RFC: Update wizard
Date: 2004-12-03 14:21:23
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E4527C96@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgadmin-hackers
 

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de] 
> Sent: 03 December 2004 13:53
> To: Dave Page
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] RFC: Update wizard
> 
> First, do we really want to hammer CVS for each update check? 
> I'd think having this in an "available versions" file is sufficient.

As long as that file can be (and is) automatically updated. 

> Second, the issue is not to retrieve a version, but to 
> identify the version of the language file currently in use. 
> We need an identifyable string inside the file for that.

More preciesly, the issue is to detect whether a file has been updated.
I suggested CVS as it should be simple to initial look for a file newer
than the releases CVS tag, and following that, newer than the one
previously downloaded. It also reduces the administration overhead.

Mind you, maybe I'm underestimating the number of users we may get.
Perhaps this should work from the ftp mirror network?

Regards, Dave.


Responses

pgadmin-hackers by date

Next:From: Dave PageDate: 2004-12-03 14:27:50
Subject: Re: New ftp layout
Previous:From: blacknozDate: 2004-12-03 14:18:37
Subject: Re: New ftp layout

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group