| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Kohei Kaigai <Kohei(dot)Kaigai(at)eu(dot)nec(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: sepgsql contrib module |
| Date: | 2011-02-15 16:06:55 |
| Message-ID: | AANLkTi=qcxr7XAtwcYL_rvp52t0Xr+i_HCwYumtFY4SC@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 15, 2011 at 11:01 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Those are good points. My point was just that you can't actually
>> build that file at the time you RUN the regression tests, because you
>> have to build it first, then install it, then run the regression
>> tests. It could be a separate target, like 'make policy', but I don't
>> think it works to make it part of 'make installcheck'.
>
> So? Once you admit that you can do that, it's a matter of a couple more
> lines to make the installcheck target depend on the policy target iff
> selinux was enabled.
Sure, you could do that, but I don't see what problem it would fix.
You'd still have to build and manually install the policy before you
could run make installcheck. And once you've done that, you don't
need to rebuild it every future time you run make installcheck.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2011-02-15 16:10:26 | Re: CommitFest 2011-01 as of 2011-02-04 |
| Previous Message | Robert Haas | 2011-02-15 16:05:22 | Re: pageinspect's infomask and infomask2 as smallint |