Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id D3BB79FB56E; Tue, 10 Apr 2007 09:55:07 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 84013-02; Tue, 10 Apr 2007 09:54:58 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 7B0769FB255; Tue, 10 Apr 2007 09:54:57 -0300 (ADT) Received: by svr2.hagander.net (Postfix, from userid 1000) id E977FDCC7D0; Tue, 10 Apr 2007 14:54:55 +0200 (CEST) Date: Tue, 10 Apr 2007 14:54:55 +0200 From: Magnus Hagander To: Dave Page , Andrew Hammond , CAJ CAJ , pgsql-general@postgresql.org, pgsql-www Subject: Re: [GENERAL] programmatic way to fetch latest release for a given major.minor version Message-ID: <20070410125455.GA26036@svr2.hagander.net> References: <1176155240.221125.319880@y80g2000hsf.googlegroups.com> <467669b30704091526v79ae044boe7217cc0777dce1f@mail.gmail.com> <5a0a9d6f0704091534i4e4af90co2dad0e9e0b60efee@mail.gmail.com> <461B3E6A.8080007@postgresql.org> <20070410081558.GB24976@svr2.hagander.net> <461B5064.8010004@postgresql.org> <20070410101852.GC24976@svr2.hagander.net> <20070410124442.GC31734@svana.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070410124442.GC31734@svana.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/25 X-Sequence-Number: 11775 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 > > trick it into RSS. > > I'd say do it in the format you're most comfortable with. Then some > XSLT wizard can convert it into RSS from there... Too late, I already did the RSS. Which was very simple, because of the RSS framework stuff already in place on the website. *However*, that one doesn't contain all the information that a program would want, and certainly not in an easily parseable format for them. It's designed for people in the other end. So I intend to do a "proper XML format" as well. //Magnus