Message-ID: <5133AD4D.3050407@agliodbs.com>
Date: Sun, 03 Mar 2013 12:06:37 -0800
From: Josh Berkus <josh@agliodbs.com>
Organization: PostgreSQL Experts Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: PostgreSQL WWW <pgsql-www@postgresql.org>
Subject: Re: Proposed changes to security.html
References: <5112B6A6.3080500@agliodbs.com> <51312CC2.70005@gmx.net>
	<51314656.1040106@agliodbs.com>
	<1362197787.11571.2.camel@vanquo.pezone.net>
In-Reply-To: <1362197787.11571.2.camel@vanquo.pezone.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org


> That might be worthwhile consideration for introductory or marketing
> material, say, but for the purpose of tracking security issues,
> "contrib" is perfectly clear: If you are installing from source, it is
> code that lives under contrib/.  If you are installing from binary, it
> is code that is in the postgresql-contrib package (usually).  Calling it
> anything other than "contrib" cannot possibly make that more clear.

Yeah, I suppose the security page is not the place to address this.  We
have a larger project problem in using three different bits of
terminology for mostly the same set of software.  We can fix the
security page once we fix the terminology in general.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


-- 
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www