| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Core Extensions relocation |
| Date: | 2011-11-18 20:36:59 |
| Message-ID: | 4EC6C1EB.8070609@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/18/11 12:27 PM, Dimitri Fontaine wrote:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> Why do you figure that, exactly? The path of least resistance will
>> be precisely to leave everything packaged as it is, in a single
>> postgresql-contrib module. I'm pretty likely to do that myself for
>> Fedora and RHEL. Subdividing/rearranging contrib makes the packager's
>> life more complicated, *and* makes his users' lives more complicated,
>> if only because things aren't where they were before. It seems unlikely
>> to happen, at least in the near term.
>
> Then if we want packagers to move, what about removing all the
> extensions not listed by Greg from the contrib/ directory and inventing
> another place where to manage them, which is not automatically built,
> but still part of buildfarm tests, if at all possible.
Actually, the whole idea is that the "Core Management Extensions" should
move from the -contrib module to the -server module. That is, those
extensions should always get installed with any server.
Of course, packagers may then reasonably ask why that code is not just
part of the core?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2011-11-18 20:47:18 | RFC: list API / memory allocations |
| Previous Message | Dimitri Fontaine | 2011-11-18 20:27:15 | Re: Core Extensions relocation |