public inbox for [email protected]  
help / color / mirror / Atom feed
From: Simon Riggs <[email protected]>
To: Devrim GÜNDÜZ <[email protected]>
Cc: Dave Page <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: Scott Mead <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Linux Downloads page change
Date: Mon, 9 Jul 2012 12:41:50 +0100
Message-ID: <CA+U5nMJqmeepcZ1vg24UrHHtKC+zXjgSy-u-peRmJNW2EFJy-A@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAKq0gvKgeckkBa0xm6xsrmNvk=Cm6zPP4n1O3CQCvDUvCYCs8w@mail.gmail.com>
	<CABUevEyONmEeqwU4VJgs8vTV3yW3dsNLPiFfPnAKJOCLgYbvYA@mail.gmail.com>
	<CAKq0gvL-s4_Mk0ztGh+yywH5v4Jvnm2Fs2k-gq2wcrW+kfY2xQ@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CA+OCxoxExqHx_ZNRpvmJpVoNCOa9yO4C3HTZ4Ob7e32Wn2+fcQ@mail.gmail.com>
	<CABUevEzm09To=uzW=+F==G98HK2YZNXsXwv+NW-7uOgqGLOxoQ@mail.gmail.com>
	<CA+OCxox1pCaXvOeVmv0gECbXsOqGeXQL-O2QsyWmFS9ZvCkjbg@mail.gmail.com>
	<CABUevEx_7-Xm+z5oc+61TuHzSbu34fWAKiRxAXjGwfCzff=OZA@mail.gmail.com>
	<CA+OCxoyGPVRQ+1tnxGuFS1JACr1QJUchS90qxXHuN_YTUNj8QA@mail.gmail.com>
	<CA+U5nMK86koEcfkBwUWRPqGTT1b8Qjp3hN=pk3to+kqaUoWp=w@mail.gmail.com>
	<CA+OCxoxxW3EOoLpWuTk=GW2Hr-Z+8m0_oN2QUQCMpVss6R+DDw@mail.gmail.com>
	<CA+U5nMKyzv6B7ywGv8BLfwig1wgimp0keo9rKUpaLpnANuiH+w@mail.gmail.com>
	<[email protected]>

On 9 July 2012 12:31, Devrim GÜNDÜZ <[email protected]> wrote:
>
> Hi Simon,
>
> On Mon, 2012-07-09 at 12:25 +0100, Simon Riggs wrote:
>
>> I am discussing the relationship of SRPMs and RPMs, which is a valid
>> point on this thread given the point that the RPMs and SRPMs have been
>> mismatched for some time and that the current process calls for manual
>> rather than automatic synchronisation.
>
> Which SRPMs are you talking about? Community SRPMs? If so, they have
> been always available on the website. If you are talking about OpenSCG
> RPMs, that is a different thing.

My words were a little unclear all round, please accept my apologies.

IMHO we should only list binaries on the postgresql.org website if
they are derived from build information that is owned by the PGDG, or
at very least publicly available at the time of the build and likely
to remain so afterwards. That process should be automatic as far as
possible, to minimise error, since the number of users of those
binaries is now very large.

Unverifiable binaries are a quality and security risk to the project.

Companies are welcome to provide value-added binaries to their
customers if they choose to do so but that should be a private matter.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



view thread (56+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Linux Downloads page change
  In-Reply-To: <CA+U5nMJqmeepcZ1vg24UrHHtKC+zXjgSy-u-peRmJNW2EFJy-A@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox