From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [sepgsql 1/3] add name qualified creation label |
Date: | 2013-01-24 04:32:24 |
Message-ID: | 26604.1359001944@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> On 17.01.2013 23:20, Kohei KaiGai wrote:
>> In addition, I forgot to update minimum required version for libselinux;
>> (it also takes change in configure script).
> libselinux1 2.1.10 or newer is a pretty tall order. That's not in debian
> testing yet, for example. I'm afraid if we bump the minimum requirement,
> what might happen is that many distributions will stop building with
> --with-selinux.
FWIW, in Fedora-land I see:
F16: 2.1.6 (F16 will go out of support next month)
F17: 2.1.10 (F17 has been stable for 6+ months)
F18: 2.1.12 (F18 just went stable)
While requiring 2.1.10 today might be thought a tad leading-edge,
will that still be true by the time we ship 9.3?
Or maybe we should just be punting this patch to 9.4, by which time the
version requirement should surely not be an issue within the community
that's likely to be using selinux at all. Unless I missed a previous
submission, this is a significant feature patch that did not show up in
time for CF3, which means that we should not be considering it at all
for 9.3 according to the rules that were agreed to in Ottawa last May.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2013-01-24 04:38:17 | Re: [sepgsql 1/3] add name qualified creation label |
Previous Message | Tom Lane | 2013-01-24 04:13:33 | Re: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review] |