From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1517 invoked by alias); 29 Mar 2003 11:22:10 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 1508 invoked from network); 29 Mar 2003 11:22:09 -0000 Received: from unknown (HELO vlsi1.ultra.nyu.edu) (128.122.140.213) by sources.redhat.com with SMTP; 29 Mar 2003 11:22:09 -0000 Received: by vlsi1.ultra.nyu.edu (4.1/1.34) id AA02443; Sat, 29 Mar 03 06:26:02 EST Date: Sat, 29 Mar 2003 15:11:00 -0000 From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner) Message-Id: <10303291126.AA02443@vlsi1.ultra.nyu.edu> To: guerby@acm.org Subject: Re: improving testing scheme (was Re: ACATS and GCC testsuite) Cc: gcc@gcc.gnu.org X-SW-Source: 2003-03/txt/msg01750.txt.bz2 You install somewhere, put in PATH, play if it, if it doesn't please you, you change your PATH, if you're short on space you delete the install location. 100% reliable, safe Nothing involving manually changing things like PATH is "100% reliable". It's always too easy to forget to change PATH or forget to change it back. A testing procedure that depends on such manual operations is inherently error-prone because of the significant risk of forgetting to do them.