From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1268 invoked by alias); 5 Feb 2004 23:01:58 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1189 invoked from network); 5 Feb 2004 23:01:57 -0000 Received: from unknown (HELO vaxjo.synopsys.com) (198.182.60.75) by sources.redhat.com with SMTP; 5 Feb 2004 23:01:57 -0000 Received: from crone.synopsys.com (crone.synopsys.com [146.225.7.23]) by vaxjo.synopsys.com (Postfix) with ESMTP id 2E732DB6F; Thu, 5 Feb 2004 15:01:57 -0800 (PST) Received: from piper.synopsys.com (localhost [127.0.0.1]) by crone.synopsys.com (8.9.1/8.9.1) with ESMTP id PAA00416; Thu, 5 Feb 2004 15:01:56 -0800 (PST) Received: (from jbuck@localhost) by piper.synopsys.com (8.11.6/8.11.6) id i15N1sL02888; Thu, 5 Feb 2004 15:01:54 -0800 X-Authentication-Warning: piper.synopsys.com: jbuck set sender to Joe.Buck@synopsys.com using -f Date: Thu, 05 Feb 2004 23:01:00 -0000 From: Joe Buck To: Gerald Pfeifer Cc: Ben Elliston , Andrew Cagney , gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com Subject: Re: DejaGnu 1.4.4 release Message-ID: <20040205150154.A2724@synopsys.com> References: <87smhxiu5d.fsf@wasabisystems.com> <40229AA6.4010005@gnu.org> <87llnhb6sq.fsf@wasabisystems.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from gp@suse.de on Thu, Feb 05, 2004 at 09:47:28PM +0100 X-SW-Source: 2004-02/txt/msg00050.txt.bz2 On Thu, Feb 05, 2004 at 09:47:28PM +0100, Gerald Pfeifer wrote: > On Thu, 6 Feb 2004, Ben Elliston wrote: > >> - should src/dejagnu/ be removed? > > What would the alternative be? To just expect (ha!) developers to > > have DejaGnu installed on their systems? The tester population is larger than the developer population. > Yes. If not right away, than in the mid term: we require casual > testers of CVS GCC to have bison and developers to have autoconf > etc.; and if upstream DejaGnu "just works", let's use that. > > Most distributions will provide DejaGnu as a package anyway. We should have a pointer on the web site to the DejaGnu source, for testers on platforms that don't have it already packaged for them.