From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Proposed changes to security.html |
Date: | 2013-03-03 20:06:37 |
Message-ID: | 5133AD4D.3050407@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-03-03 22:16:12 | Ooops! Minor issue with email address mangling |
Previous Message | Josh Kupershmidt | 2013-03-02 22:02:28 | Re: msgtxt.php archive links broken |