From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Darren Duncan <darren(at)darrenduncan(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: deprecating contrib for PGXN |
Date: | 2011-05-18 17:23:45 |
Message-ID: | 2918.1305739425@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)kineticode(dot)com> writes:
> On May 18, 2011, at 10:30 AM, Dimitri Fontaine wrote:
>> The other problem is that the facility we need to provide the most is
>> binary distributions (think apt-get). Lots of site won't ever compile
>> stuff on their production servers. So while PGXN is a good tool, it's
>> not a universal answer.
> Yeah, I would think that, *if* we were to seriously look at deprecating contrib (and I'm not suggesting that at all), one would *first* need to solve the binary distribution problems.
> I think building tools so that PGXN distributions are automatically harvested and turned into StackBuilder/RPM/.deb binaries would be the place to start on that.
Hmmm ... I think the real point of those policies about "no source
builds" is to ensure that their systems are only running code that's
been vetted to some degree by a responsible person (ie, an authorized
packager for whatever distro they run). So any sort of automated
collection of packages would go directly against what the policies are
trying to accomplish, and would likely lead to the policies being
amended to specifically ban use of your repo :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David E. Wheeler | 2011-05-18 17:29:06 | Re: deprecating contrib for PGXN |
Previous Message | Selena Deckelmann | 2011-05-18 17:23:11 | Re: Adding an example for replication configuration to pg_hba.conf |