Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree) - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)
Date
Msg-id CAB7nPqT-00fQ1qfumVskFp9PoH0+hsY4DSxejjr37SkwBAgEFw@mail.gmail.com
Whole thread Raw
In response to Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Mon, Feb 23, 2015 at 12:00 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On 2/22/15 5:41 AM, Michael Paquier wrote:
>>> You could argue that these .gitignore files don't actually belong there,
>>> but your patch doesn't change or move those files, and even modules that
>>> have non-empty sql/ or expected/ directories have .gitignore files
>>> there, so it is considered the appropriate location.
>>
>> This is up to the maintainer of each extension to manage their code
>> tree. However I can imagine that some people would be grateful if we
>> allow them to not need sql/ and expected/ containing only one single
>> .gitignore file ignoring everything with "*", making the code tree of
>> their extensions cleaner.
>
> I would like to have an extension in tree that also does this, so we
> have a regression test of this functionality.

Sure. Here is one in the patch attached added as a test module. The
name of the module is regress_dynamic. Perhaps the name could be
better..
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Venkata Balaji N
Date:
Subject: Re: Redesigning checkpoint_segments
Next
From: Corey Huinker
Date:
Subject: Re: dblink: add polymorphic functions.