Date: Mon, 29 Mar 1999 15:10:11 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Andris Pavenis <pavenis AT lanet DOT lv>
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP support in standard EGCS 1.1.2
In-Reply-To: <Pine.A41.4.05.9903290940340.69178-100000@ieva01.lanet.lv>
Message-ID: <Pine.SUN.3.91.990329150949.9091R-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 29 Mar 1999, Andris Pavenis wrote:

> There are many LFN related problems with original egcs sources (including
> header STL and libg++ header files. Therefore I don't think we'll be able
> to rename them all in original egcs sources. Therefore I suggest to sty
> with current approach: running some shell script that modifies egcs
> sources (together with related packages) for DJGPP.

Why do you think it will be impossible to rename the offending files
in the official distribution?  Did you try and were turned down?

My experience is that such renaming is possible, and that GNU
maintainers are usually cooperative.  The number of the offending
files is not a factor: just create a list of all of them, with
suggested alternative names, and mail them to the maintainers.

Having the official distribution rely on LFN means that a constant
effort is required to adjust the renaming scripts to each new release.
This effectively means that the port dies within months after the
current maintainer (you) leaves DJGPP.  Please think a bit about the
posterity.