From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55794) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RW6tU-0004ZX-OK for qemu-devel@nongnu.org; Thu, 01 Dec 2011 08:41:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RW6tL-00028M-8p for qemu-devel@nongnu.org; Thu, 01 Dec 2011 08:41:44 -0500 Received: from mx1.redhat.com ([209.132.183.28]:51566) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RW6tK-000289-RL for qemu-devel@nongnu.org; Thu, 01 Dec 2011 08:41:35 -0500 From: Lucas Meneghel Rodrigues Date: Thu, 1 Dec 2011 11:41:22 -0200 Message-Id: <1322746884-8723-1-git-send-email-lmr@redhat.com> Subject: [Qemu-devel] [PATCH 0/2] qemu-io tests: More fine grained control of qemu paths List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: kwolf@redhat.com, Lucas Meneghel Rodrigues , hch@lst.de, kvm@vger.kernel.org In automated test environments, we often build and test qemu from arbitrary paths, rather than installing them on standard PATH directories. Of course, appending directories to PATH might produce the desired result, but making it possible to specify arbitrary qemu paths through environment variables is very convenient and minimally intrusive. So, make it possible to set qemu paths through env variables, and also, print the paths of the qemu versions being tested, for clarity sake. Lucas Meneghel Rodrigues (2): check: print relevant path information common.config: Allow use of arbitrary qemu* paths check | 3 +++ common.config | 12 +++++++++--- 2 files changed, 12 insertions(+), 3 deletions(-) -- 1.7.7.3