Subject: Re: ANNOUNCE: DJGPP port of GNU Bison 1.29 uploaded
From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To: djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.1010913083700.28956B-100000@is>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010913083700 DOT 28956B-100000 AT is>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.13.99+cvs.2001.09.11.22.18 (Preview Release)
Date: 13 Sep 2001 09:17:41 +0200
Message-Id: <1000365462.29678.3.camel@bender.falconsoft.be>
Mime-Version: 1.0
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

On Thu, 2001-09-13 at 08:39, Eli Zaretskii wrote:
> 
> I can't say I'm happy with this change.  It could easily cause subtle 
> problems for those who don't follow instructions.  It also means removing 
> these lines from djgpp.env in the next DJGPP release means we could break
> Bison for people who don't upgrade Bison when they download djdev204.zip.
> 
> Why was this change necessary?

Probably to fall in line with the canonical GNU file locations (i.e.
$prefix/share/$package for package-specific files); and having /dev/env
support makes that possible.
Having these settings in djgpp.env was probably a mistake anyway;
overrides like that always make creating a cleaner port harder (for
exactly the reasons you give).