From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: RFC: Update wizard |
Date: | 2004-12-03 13:52:33 |
Message-ID: | 41B06FA1.4010900@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
>>Sent: 03 December 2004 13:19
>>To: Dave Page
>>Cc: pgadmin-hackers
>>Subject: Re: [pgadmin-hackers] RFC: Update wizard
>>
>>
>>>No, it doesn't, unless it finds a placeholder such as $Id.
>>
>>Even then,
>>
>>>I don't think it does so for binary files.
>>
>>Of course $Id would be necessary. But if CVS doesn't stamp
>>the file, how do you want CVS to handle the revision marking?
>
>
> CVS doesn't have to mark the file internally. Consider what happens if
> you try to check out a specific revision of a file - we can do that via
> the web, eg:
>
> http://cvs.pgadmin.org/cgi-bin/viewcvs.cgi/pgadmin3/src/ui/ar_SA/pgadmin
> 3.po?rev=1.20
>
> Gets us rev 1.20.
>
> In a similar was it shouldn't be difficult to query cvs for the latest
> version number of a given file.
First, do we really want to hammer CVS for each update check? I'd think
having this in an "available versions" file is sufficient.
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.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2004-12-03 13:53:10 | Re: Statistics logging of auto update http queries |
Previous Message | Dave Page | 2004-12-03 13:47:43 | Re: New ftp layout |