| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: [HACKERS] plperl and pltcl installcheck targets |
| Date: | 2005-05-14 17:59:54 |
| Message-ID: | 4805.1116093594@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> OK, here's what I have. The tgz file contains the sql and expected
> directories for the 3 PLs, plus there's a patch for the makefiles.
Applied with minor editorialization to make it more like the contrib
installcheck process.
I added a "make installcheck" target in the src/pl directory, so that
you can just fire that one make instead of having to check which PLs
are actually configured.
It occurs to me that maybe we should just add src/pl to the toplevel
installcheck target, which would make the whole thing pretty
automatic. However, contrib isn't in that target, so maybe the PLs
shouldn't be either. Thoughts?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-05-14 18:36:36 | Re: [HACKERS] plperl and pltcl installcheck targets |
| Previous Message | Bruce Momjian | 2005-05-14 16:31:22 | Re: Best way to scan on-disk bitmaps |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-05-14 18:36:36 | Re: [HACKERS] plperl and pltcl installcheck targets |
| Previous Message | Andrew Dunstan | 2005-05-14 15:49:01 | [Fwd: Re: [HACKERS] plperl and pltcl installcheck targets] |