Horton

Re: sepgsql contrib module

Alvaro Herrera <alvherre@commandprompt.com>

View thread
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Kohei Kaigai <kohei.kaigai@eu.nec.com>
Cc: Stephen Frost <sfrost@snowman.net>, Robert Haas <robertmhaas@gmail.com>, KaiGai Kohei <kaigai@kaigai.gr.jp>, PgHacker <pgsql-hackers@postgresql.org>
Date: 2011-02-14T19:01:36Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. pgindent run for 9.0, second run

Excerpts from Kohei Kaigai's message of lun feb 14 13:47:58 -0300 2011:
> > We really need to get a buildfarm which is building with this.  To that
> > end, would you mind providing directions so someone else could set up a
> > buildfarm member to test it..?
> 
> It seems to me not difficult to describe a direction to build, install and
> run regression test.
> Do we have any Fedora 14 environment in the buildfarm?
> It is the most suitable distribution to set up sepgsql module, because the
> default installation already has selinux configurations.

It would be good to fix the Makefile problem that prevents the code to
build elsewhere.  There's another thread about a hardcoded path to a
system Makefile in contrib/sepgsql that causes that module to FTBFS.  Is
there a way to fix that?  I had a look some days ago and it didn't seem
like there was a way to query the system for the proper path to use.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support