Re: PL contribution guidelines?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: mlg3 <mlg3(at)mail15(dot)com>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PL contribution guidelines?
Date: 2003-09-25 11:12:25
Message-ID: Pine.LNX.4.44.0309251307270.29298-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

mlg3 writes:

> 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])

There is currently some disagreement about whether every now procedural
language implementation should be included in the core distribution. If
you choose to distribute your package separately, you can take a look at
http://developer.postgresql.org/~petere/plsh.html as an example for how to
package it.

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

I think there is enough documentation about this already. Creating a PL
handler is not a common task. But if you have concrete points that you
would like to have mentioned somewhere, please tell us about them.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2003-09-25 12:23:11 Re: NuSphere and PostgreSQL for windows
Previous Message Zeugswetter Andreas SB SD 2003-09-25 09:57:26 Re: More Prelimiary DBT-2 Test Results with PostgreSQL 7.3.4