From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Larry Rosenman <ler(at)lerctr(dot)org>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: [PATCHES] Makefile.PL for Pg.so |
Date: | 2001-08-26 16:11:25 |
Message-ID: | 18716.998842285@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Another fun feature of the DESTDIR build environment is that the
> writability test of the target directory will most likely fail because it
> doesn't exist at all.
> I've been thinking how I'd like to fix this: We add an option to
> configure that says to *not* install the Perl module into the standard
> Perl tree, but instead somewhere under our own $prefix. That way people
> that don't have root access can use this option and still install the
> whole tree in one run. But then we'd remove that writability check and
> people that have root access or failed to use that option will get a hard
> failure. This would create a much more reliable and predictable build
> environment.
Why would we remove the writability check? Perhaps it needs to be
extended to recognize the case of target-dir-doesn't-exist-but-can-be-
created, but I don't see why a hard failure is better.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-08-26 16:49:22 | Re: C++ and bool constants (was Re: [NOVICE] gcc 3.0.1) |
Previous Message | Peter Eisentraut | 2001-08-26 12:37:25 | Re: Re: [PATCHES] Makefile.PL for Pg.so |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-08-26 17:09:29 | Re: [JDBC] Re: Bug #428: Another security issue with the JDBC driver. |
Previous Message | Peter Eisentraut | 2001-08-26 12:37:25 | Re: Re: [PATCHES] Makefile.PL for Pg.so |