| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] plperl and pltcl installcheck targets |
| Date: | 2005-05-14 18:53:56 |
| Message-ID: | 42864944.80405@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut wrote:
>Tom Lane wrote:
>
>
>>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?
>>
>>
>
>Contrib isn't built by default, so it isn't tested by default. But the
>PLs that are built should also be tested, I think.
>
>
>
I agree. That will also mean that buildfarm members will automatically
start doing the checks (as long as they are set up to build the PLs), so
it would be an extra bonus for me :-)
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-14 19:46:19 | Re: [HACKERS] plperl and pltcl installcheck targets |
| Previous Message | Peter Eisentraut | 2005-05-14 18:36:36 | Re: [HACKERS] plperl and pltcl installcheck targets |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-14 19:46:19 | Re: [HACKERS] plperl and pltcl installcheck targets |
| Previous Message | Peter Eisentraut | 2005-05-14 18:36:36 | Re: [HACKERS] plperl and pltcl installcheck targets |