PL contribution guidelines? - Mailing list pgsql-hackers

From mlg3
Subject PL contribution guidelines?
Date
Msg-id 200309250736.h8P7aewA087369@www.mail15.com
Whole thread Raw
Responses Re: PL contribution guidelines?
List pgsql-hackers
I want to make a contribution.
It is a new (to pgsql) procedural language.
Currently it already works (but debugging output 
is not disabled yet).

I've got some questions and considerations, please, correct me
if I am wrong:

I understand that pgsql uses autoconf but not other autotools.
The best location for such contribution is in
src/pl/pl<lang-name>

Now, how do I include my PL into the build list?
What files must I provide? (preferrably, by borrowing
them from another PL, e.g. PLPERL or TCL])

Currently, I compile the C source by hands:
cc -fpic -I /pgsql/src/include -c plpfe.c
cc -shared -Wl,--rpath -Wl,/usr/local/lib -Wl,--rpath -Wl,
/usr/local/lib/pfe -o plpfe.so plpfe.o -lpfe

One part of the implementation resides in the pfe build tree,
but it needs postgres.h and fmgr.h

Currently I use
#include "/pgsql/src/include/postgres.h"
#include "/pgsql/src/include/fmgr.h"
(/pgsql is a symlink to the PostgreSQL*.*.* directory)
but IMO there should be a better way.

Should I publish the project as plpfe.sf.net, or there's
a better location?

I also composed PLSAMPLE (the same implementation
components, but empty). IMO, it (PLSAMPLE) also should be 
there in the PSQL distribution.


regards, mlg


pgsql-hackers by date:

Previous
From: "Heikki Tuuri"
Date:
Subject: Re: PostgreSQL not ACID compliant?
Next
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: More Prelimiary DBT-2 Test Results with PostgreSQL 7.3.4