Message-ID: <8D53104ECD0CD211AF4000A0C9D60AE35C1E68@probe-2.acclaim-euro.net>
From: Shawn Hargreaves <ShawnH AT Probe DOT co DOT uk>
To: djgpp AT delorie DOT com
Cc: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Subject: Re: Announcing Allegro 3.11
Date: Mon, 1 Mar 1999 11:25:09 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1460.8)
Content-Type: text/plain
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii writes:
>>    Renamed the ChangeLog file to CHANGES, to avoid problems on 8.3 
>>    systems.
>
> What problems are these?  All GNU packages have a ChangeLog in their
> distributions, but I never heard about any problems.

Partly it just looked ugly if it got truncated to changelo, but the
real problem came when people tried to apply a patch to upgrade their
Allegro version. If they originally unzipped it with a non-LFN 
utility like pkzip, they would have a changelo file, but then when 
they run the djgpp patch utility, it will be unable to find the full 
ChangeLog, so the patch will fail.

This is really just a user error, but it can easily be avoided if I
keep all the names to an 8.3 format, and this saves me having to
endlessly answer the same question from people who can't apply the
patch :-)


	Shawn Hargreaves.