Обсуждение: Re: RSS should contain URL to source code [PATCH]
Ok,
I got some spare time and whipped up the attached patch.
comments, suggestions?
- Martin -
I got some spare time and whipped up the attached patch.
comments, suggestions?
- Martin -
On Fri, Oct 8, 2010 at 10:08 AM, Martin Atukunda <matlads@gmail.com> wrote:
Yes, you are right. I wanted the convenience of getting directly to
the source of the correct version.
But on second thought, I don't see why we can't _also_ include the
link to the generic download page.
- Martin -
On Thu, Oct 7, 2010 at 7:36 PM, Magnus Hagander <magnus@hagander.net> wrote:
> On Thu, Oct 7, 2010 at 15:32, Martin Atukunda <matlads@gmail.com> wrote:
>> Hi,
>>
>> The most recent releases for postgresql are available via RSS URL
>> http://www.postgresql.org/versions.rss. This RSS feed is already very
>> useful (the link for each entry points to the release notes for that
>> release of postgresql)
>>
>> But the description of each item on the RSS feed is simply the text
>>
>> -- 8< --
>> MAJOR.MINOR.RELEASE is the latest release in the MAJOR.MINOR series.
>> -- >8 --
>>
>> I'd like to propose that the description be extended a little to
>> include the URL from which to download the source code. Something like
>> this:
>>
>> -- 8< --
>> MAJOR.MINOR.RELEASE is the latest release in the MAJOR.MINOR series.
>>
>> Grab it from here:
>> ftp://ftp.postgresql.org/pub/source/vMAJOR.MINOR.RELEASE/postgresql-MAJOR.MINOR.RELEASE.tar.gz
>> -- >8 --
>
> Why the source, and not binaries? And once we open that can of work,
> there'll be lots of it. I guess we could add a link to
> http://www.postgresql.org/download, but I have a feeling the part
> you're after is not to have to browse but get directly to the correct
> version?
>
> --
> Magnus Hagander
> Me: http://www.hagander.net/
> Work: http://www.redpill-linpro.com/
>
Вложения
I still don't see the point, and find it rather inconsistent to just list the source and nothing else. Given that the vast majority of our users will be intersted in the binaries and not the source. And from experience, I'm worried about hardcoding paths on our ftp site, since they tend to sometimes be. um. inconsistent. though that has gotten a lot better lately. If others find it useful I won't veto it, though :-) //Magnus On Thu, Nov 11, 2010 at 08:35, Martin Atukunda <matlads@gmail.com> wrote: > Ok, > > I got some spare time and whipped up the attached patch. > > comments, suggestions? > > - Martin - > > On Fri, Oct 8, 2010 at 10:08 AM, Martin Atukunda <matlads@gmail.com> wrote: >> >> Yes, you are right. I wanted the convenience of getting directly to >> the source of the correct version. >> >> But on second thought, I don't see why we can't _also_ include the >> link to the generic download page. >> >> - Martin - >> >> On Thu, Oct 7, 2010 at 7:36 PM, Magnus Hagander <magnus@hagander.net> >> wrote: >> > On Thu, Oct 7, 2010 at 15:32, Martin Atukunda <matlads@gmail.com> wrote: >> >> Hi, >> >> >> >> The most recent releases for postgresql are available via RSS URL >> >> http://www.postgresql.org/versions.rss. This RSS feed is already very >> >> useful (the link for each entry points to the release notes for that >> >> release of postgresql) >> >> >> >> But the description of each item on the RSS feed is simply the text >> >> >> >> -- 8< -- >> >> MAJOR.MINOR.RELEASE is the latest release in the MAJOR.MINOR series. >> >> -- >8 -- >> >> >> >> I'd like to propose that the description be extended a little to >> >> include the URL from which to download the source code. Something like >> >> this: >> >> >> >> -- 8< -- >> >> MAJOR.MINOR.RELEASE is the latest release in the MAJOR.MINOR series. >> >> >> >> Grab it from here: >> >> >> >> ftp://ftp.postgresql.org/pub/source/vMAJOR.MINOR.RELEASE/postgresql-MAJOR.MINOR.RELEASE.tar.gz >> >> -- >8 -- >> > >> > Why the source, and not binaries? And once we open that can of work, >> > there'll be lots of it. I guess we could add a link to >> > http://www.postgresql.org/download, but I have a feeling the part >> > you're after is not to have to browse but get directly to the correct >> > version? >> > >> > -- >> > Magnus Hagander >> > Me: http://www.hagander.net/ >> > Work: http://www.redpill-linpro.com/ >> > > > > > -- > Sent via pgsql-www mailing list (pgsql-www@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-www > > -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
On Wed, Nov 17, 2010 at 9:56 AM, Magnus Hagander <magnus@hagander.net> wrote: > I still don't see the point, and find it rather inconsistent to just > list the source and nothing else. Given that the vast majority of our > users will be intersted in the binaries and not the source. > > And from experience, I'm worried about hardcoding paths on our ftp > site, since they tend to sometimes be. um. inconsistent. though that > has gotten a lot better lately. Those would be my two concerns. Source code just isn't that useful for most of our users. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company