Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Listmail
I love Open Source XD http://ethan.tira-thompson.com/cvslog2web/ Note that this is overkill (but it would look SEXY on the site). However, the original poster probably wants to know when to update his servers, so he won't care about CVS commits... If there was a RSS

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Jorge Godoy
Listmail <[EMAIL PROTECTED]> writes: >>> Yeah yeah, but terminology aside, having 2 or three digits in each >>> attribute is just wrong! >> >> Terminology aside, why? The unit is "8.1" not "8" and "1". It makes no >> sense to say you're on version 8, in the given context, so why should the >> XML

Re: [pgsql-www] Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Dave Page
Alvaro Herrera wrote: > It makes sense to store things separately when they have a semantic > difference. What we call "major" is the first two digits and dot. We > call "minor" to the third digit, and that's all. We don't have > "revisions". This is how it has ever been and we even document it

Re: [pgsql-www] Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > It makes sense to store things separately when they have a semantic > difference. What we call "major" is the first two digits and dot. We > call "minor" to the third digit, and that's all. We don't have > "revisions". This is how it has ever been an

Re: [pgsql-www] Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Alvaro Herrera
Dave Page escribió: > Alvaro Herrera wrote: > > Dave Page escribió: > >> Magnus Hagander wrote: > >>> That is actually precisely my point. It makes *no sense* to filter based > >>> on > >>> 8.x. 8.0 is no more a major release than 7.4. > >> Yes it is - that's precisely why it was 8.0 and not 7.5.

Re: [pgsql-www] Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Dave Page
Alvaro Herrera wrote: > Dave Page escribió: >> Magnus Hagander wrote: >>> That is actually precisely my point. It makes *no sense* to filter based on >>> 8.x. 8.0 is no more a major release than 7.4. >> Yes it is - that's precisely why it was 8.0 and not 7.5. > > That was merely a marketing artif

Re: [pgsql-www] Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Alvaro Herrera
Dave Page escribió: > Magnus Hagander wrote: > > That is actually precisely my point. It makes *no sense* to filter based on > > 8.x. 8.0 is no more a major release than 7.4. > > Yes it is - that's precisely why it was 8.0 and not 7.5. That was merely a marketing artifact; it was called 7.5 unti

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Dave Page
Magnus Hagander wrote: > That is actually precisely my point. It makes *no sense* to filter based on > 8.x. 8.0 is no more a major release than 7.4. Yes it is - that's precisely why it was 8.0 and not 7.5. /D ---(end of broadcast)--- TIP 1: if pos

Re: [pgsql-www] Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Peter Eisentraut
Am Dienstag, 10. April 2007 13:35 schrieb Dave Page: > Imagine wanting to display only the details of the 8.x releases on a > site for example. In your schema, you'd have to use a substring match on > an attribute value to filter out 6.x and 7.x. That use case is just as valid as wanting to show o

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Magnus Hagander
On Tue, Apr 10, 2007 at 02:44:42PM +0200, Martijn van Oosterhout wrote: > On Tue, Apr 10, 2007 at 12:18:52PM +0200, Magnus Hagander wrote: > > But given that we might want to add things like this, having our own custom > > XML format certainly makes a bit more sense, it might be harder to try to >

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Martijn van Oosterhout
On Tue, Apr 10, 2007 at 12:18:52PM +0200, Magnus Hagander wrote: > But given that we might want to add things like this, having our own custom > XML format certainly makes a bit more sense, it might be harder to try to > trick it into RSS. I'd say do it in the format you're most comfortable with.

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Magnus Hagander
On Tue, Apr 10, 2007 at 12:35:38PM +0100, Dave Page wrote: > Magnus Hagander wrote: > > Terminology aside, why? The unit is "8.1" not "8" and "1". It makes no > > sense to say you're on version 8, in the given context, so why should the > > XML data pretend there is? > > Because serving the data i

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Listmail
Yeah yeah, but terminology aside, having 2 or three digits in each attribute is just wrong! Terminology aside, why? The unit is "8.1" not "8" and "1". It makes no sense to say you're on version 8, in the given context, so why should the XML data pretend there is? //Magnus Just prete

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Dave Page
Magnus Hagander wrote: > Terminology aside, why? The unit is "8.1" not "8" and "1". It makes no > sense to say you're on version 8, in the given context, so why should the > XML data pretend there is? Because serving the data in the decomposed format gives the consumer the maximum flexibility to d

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Magnus Hagander
On Tue, Apr 10, 2007 at 12:03:44PM +0100, Dave Page wrote: > Magnus Hagander wrote: > > On Tue, Apr 10, 2007 at 09:52:52AM +0100, Dave Page wrote: > >> Magnus Hagander wrote: > >>> 2) Create a new file with a specific schema. Something like: > >>> > >>> > >>> > >>> > >>> This is the most ligh

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Dave Page
Magnus Hagander wrote: > On Tue, Apr 10, 2007 at 09:52:52AM +0100, Dave Page wrote: >> Magnus Hagander wrote: >>> 2) Create a new file with a specific schema. Something like: >>> >>> >>> >>> >>> This is the most lightweight solution. >> More like: >> >> >> >> >> > > But that doesn't

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Magnus Hagander
On Tue, Apr 10, 2007 at 11:09:50AM +0200, Listmail wrote: > > I love Open Source XD > > http://ethan.tira-thompson.com/cvslog2web/ Hmm. Don't tell people about my secret plans :) (Though I hadn't looked at that piece of software in particylar) > Note that this is overkill (bu

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Magnus Hagander
On Tue, Apr 10, 2007 at 09:52:52AM +0100, Dave Page wrote: > Magnus Hagander wrote: > > 2) Create a new file with a specific schema. Something like: > > > > > > > > > > This is the most lightweight solution. > > More like: > > > > > But that doesn't reflect our terminology. Per our

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Dave Page
Magnus Hagander wrote: > 2) Create a new file with a specific schema. Something like: > > > > > This is the most lightweight solution. More like: But I can't help thinking that we should have some additional values for release notes, download sub-URLs (to be appended to the mirror

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Magnus Hagander
On Tue, Apr 10, 2007 at 08:36:10AM +0100, Dave Page wrote: > Andrew Hammond wrote: > > On 4/9/07, CAJ CAJ <[EMAIL PROTECTED]> wrote: > >> On 9 Apr 2007 14:47:20 -0700, Andrew Hammond > >> <[EMAIL PROTECTED]> wrote: > >> > I'm writing a script that wants to know the latest release for a given > >> >

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-10 Thread Dave Page
Andrew Hammond wrote: > On 4/9/07, CAJ CAJ <[EMAIL PROTECTED]> wrote: >> On 9 Apr 2007 14:47:20 -0700, Andrew Hammond >> <[EMAIL PROTECTED]> wrote: >> > I'm writing a script that wants to know the latest release for a given >> > major.minor version. Is there some better way than parsing >> > http:/

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-09 Thread Listmail
Here you go. Fetches versions and prints most recent minor for each major Tests all mirrors for speed and prints out the 4 fastest (takes some time) http://www.crummy.com/software/BeautifulSoup/ Have a nice day ! #! /bin/env python # -*- coding: utf-8 -

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-09 Thread Alvaro Herrera
Andrew Hammond escribió: > On 4/9/07, CAJ CAJ <[EMAIL PROTECTED]> wrote: > >On 9 Apr 2007 14:47:20 -0700, Andrew Hammond > ><[EMAIL PROTECTED]> wrote: > >> I'm writing a script that wants to know the latest release for a given > >> major.minor version. Is there some better way than parsing > >> htt

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-09 Thread Andrew Hammond
On 4/9/07, CAJ CAJ <[EMAIL PROTECTED]> wrote: On 9 Apr 2007 14:47:20 -0700, Andrew Hammond <[EMAIL PROTECTED]> wrote: > I'm writing a script that wants to know the latest release for a given > major.minor version. Is there some better way than parsing > http://www.postgresql.org/ftp/source/ or tr

Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version

2007-04-09 Thread CAJ CAJ
On 9 Apr 2007 14:47:20 -0700, Andrew Hammond < [EMAIL PROTECTED]> wrote: I'm writing a script that wants to know the latest release for a given major.minor version. Is there some better way than parsing http://www.postgresql.org/ftp/source/ or trying to connect to ftp (which is invariably timing