Peter Eisentraut <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
