From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4266 invoked by alias); 16 Jun 2004 16:30:03 -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 3966 invoked from network); 16 Jun 2004 16:29:57 -0000 Received: from unknown (HELO vaxjo.synopsys.com) (198.182.60.75) by sourceware.org with SMTP; 16 Jun 2004 16:29:57 -0000 Received: from mother.synopsys.com (mother.synopsys.com [146.225.100.171]) by vaxjo.synopsys.com (Postfix) with ESMTP id 3C1FFDB3A; Wed, 16 Jun 2004 09:29:55 -0700 (PDT) Received: from piper.synopsys.com (localhost [127.0.0.1]) by mother.synopsys.com (8.9.1/8.9.1) with ESMTP id JAA07654; Wed, 16 Jun 2004 09:29:54 -0700 (PDT) Received: (from jbuck@localhost) by piper.synopsys.com (8.11.6/8.11.6) id i5GGTrR16286; Wed, 16 Jun 2004 09:29:53 -0700 X-Authentication-Warning: piper.synopsys.com: jbuck set sender to Joe.Buck@synopsys.com using -f Date: Wed, 16 Jun 2004 16:30:00 -0000 From: Joe Buck To: Alexandre Oliva Cc: Ben Elliston , Joel Brobecker , Zack Weinberg , gcc@gcc.gnu.org, gdb@sources.redhat.com, binutils@sources.redhat.com Subject: Re: PROPOSAL: removing src/expect Message-ID: <20040616092953.B13335@synopsys.com> References: <20040615141501.A19302@mailhub.air.net.au> <87zn74zevv.fsf@taltos.codesourcery.com> <20040615154957.A5587@synopsys.com> <20040616133517.A26041@mailhub.air.net.au> <20040616061117.GA1502@gnat.com> <20040616161454.A26988@mailhub.air.net.au> 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 aoliva@redhat.com on Wed, Jun 16, 2004 at 04:08:27AM -0300 X-SW-Source: 2004-06/txt/msg00180.txt.bz2 On Wed, Jun 16, 2004 at 04:08:27AM -0300, Alexandre Oliva wrote: > On Jun 16, 2004, Ben Elliston wrote: > > > I meant who is going to keep src/expect up to date? The version > > that's there has not been touched since the initial sourceware import > > in November 1999. > > Do we have evidence that it's broken? If so, we do need an update. > If not, why can't we just leave it at the working state? Yes, last I checked it resulted in failures on Solaris that I don't see with version 5.40.0 (that is, when I switched from the infrastructure version of expect to the official one, I suddenly no longer saw lots of Java failures for Solaris).