Date: Thu, 15 Nov 2001 14:36:33 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Juan Manuel Guerrero <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
cc: Prashant TR <tr AT yahoo-inc DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: small comment about shl20b.zip
In-Reply-To: <CE959467C17@HRZ1.hrz.tu-darmstadt.de>
Message-ID: <Pine.SUN.3.91.1011115143321.14688E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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, 15 Nov 2001, Juan Manuel Guerrero wrote:

> 1) No DJGPP port, no matter if it supports or not NLS,
>    should install a charset.alias file in lib.

I agree with the goal, but the question is: is that goal reasonably 
reachable?  If not, we are asking package maintainers something they
cannot easily provide.

The problem, as I recall it, is that "make install" installs that file.  
If that is true, we should do something to prevent that.

> 2) The only ports that will continuosly provide an up to date charset.alias file,
>    and will install them in lib, are gettext and libiconv.

Perhaps gettext and libiconv should make this file read-only.  This way, 
the users will at least see a warning (or would they?).