From dev-return-8613-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Fri Dec 06 11:26:49 2002 Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 21019 invoked by uid 500); 6 Dec 2002 11:26:48 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 21006 invoked from network); 6 Dec 2002 11:26:48 -0000 Date: Fri, 6 Dec 2002 12:26:30 +0100 (CET) From: Dirk-Willem van Gulik To: Aaron Bannert cc: dev@apr.apache.org Subject: Re: APR_TMP_DIRECTORY In-Reply-To: <8AE6141E-0898-11D7-9902-000393B3C494@clove.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Can a single temp directory be discovered by autoconf at build time and > still apply for binary distributions? (Are there platforms where the > same binary would work but the default temp dir might change?) In any serious shop: Your run time system in production is generally != build system. And if it is - then I'd worry :-) The first may be largely read-only disks, have complex NFS interaction and what not. Whereas the latter may actually have things like a compiler and normal disk space. Operational choises, such as where /tmp is - should NEVER be left to autoconf. Autoconf should only be used for things which are immutable properties of a specific version/incarnation of the operating system. Dw