| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mark Mielke <mark(at)mark(dot)mielke(dot)cc>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Managing multiple branches in git |
| Date: | 2009-06-03 00:00:09 |
| Message-ID: | 20090603000009.GN5845@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost escribió:
> I hope this isn't anything particularly special because I feel like I've
> been doing it forever, but..
>
> ==# cvs -z3 co pgsql
> ==# mkdir pgsql.build
> ==# cd pgsql.build
> ==# ../pgsql/configure --my-args-here
> ==# make
> ...
>
> Keeps all the build files and everything in pgsql.build and leaves the
> pgsql directory pristine.. I've pretty much always done things this way
> so I guess I just assumed it was common. Maybe it's not what you're
> looking for though.
This doesn't fully work because some files are created in the source
directory even when building outside (e.g. src/backend/parser/scan.c)
(I work like this all the time too, except that I keep my trees in
.../pgsql/source/00head and they build to .../pgsql/build/00head)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-03 00:01:32 | Re: Managing multiple branches in git |
| Previous Message | Alvaro Herrera | 2009-06-02 23:54:50 | Re: Managing multiple branches in git |