X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Wed, 20 Feb 2002 20:31:09 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: "Juan Manuel Guerrero" Message-Id: <2950-Wed20Feb2002203109+0200-eliz@is.elta.co.il> X-Mailer: emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9 CC: sandmann AT clio DOT rice DOT edu, djgpp-workers AT delorie DOT com In-reply-to: <278A40F3FB0@HRZ1.hrz.tu-darmstadt.de> (st001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De) Subject: Re: bison and djgpp.env References: <1676-Tue19Feb2002213757+0200-eliz AT is DOT elta DOT co DOT il> from "Eli Zaretskii" at Feb 19, 2002 09:37:58 PM <278A40F3FB0 AT HRZ1 DOT hrz DOT tu-darmstadt DOT de> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: "Juan Manuel Guerrero" > Date: Wed, 20 Feb 2002 18:33:57 +0100 > > The only port that may stop working is bison 1.28. But even this port can be > recompiled with it own canonical path. If such an updated port is uploaded > to simtelnet there would be no longer the need of an bison specific entry in > djgpp.env. You forget about users who already have Bison 1.2x installed on their systems. Removing Bison 1.28 from SimTel or uploading a refreshed binary won't change the behavior of the installed binaries. I don't think it's right to break a user's installation when she installs a new djdev.