From:	Bruno Haible <haible AT ilog DOT fr>
MIME-Version:	1.0
Message-ID:	<15002.28215.961848.395747@honolulu.ilog.fr>
Date:	Mon, 26 Feb 2001 15:54:47 +0100 (CET)
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De, djgpp-workers AT delorie DOT com
Subject:	Re: DJGPP specific patch for libiconv-1.5.1
In-Reply-To:	<2593-Sat24Feb2001102921+0200-eliz@is.elta.co.il>
References:	<2D6331E258B AT HRZ1 DOT hrz DOT tu-darmstadt DOT de>
	<2593-Sat24Feb2001102921+0200-eliz AT is DOT elta DOT co DOT il>
X-Mailer:	VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid
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

Eli Zaretskii writes:

> >    To resolve the name conflict, new directories are created while unzipping.
> >    Filenames like iso8895_XX.h resolve to the same filename iso8895_.h
> >    on plain DOS. This can be avoided by extracting this files into a new
> >    directory. Example:
> >      lib/iso8859_XX.h    become lib/ISO/8859_XX.h
> >      lib/iso2022_XXXX.h  become lib/ISO/2022_XXXX.h
> >      lib/isoir165XXX.h   become lib/ISO/ir165XXX.h
> 
> Why cannot the official package be restructured so that it already has
> all those directories?

This is unacceptable. It is exactly what I mean with "unduly
restrictions for the maintainer".

Bruno

- Raw text -