Message-ID: <000801c16dfa$19ab68c0$96b4c5cb@home-computer>
From: "Prashant TR" <tr AT yahoo-inc DOT com>
To: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>, <djgpp-workers AT delorie DOT com>
Cc: "Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>,
   "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Subject: Re: small comment about shl20b.zip
Date: Thu, 15 Nov 2001 22:52:25 +0530
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Reply-To: djgpp-workers AT delorie DOT com

>On Thu, 2001-11-15 at 13:36, Eli Zaretskii wrote:
>>
>> 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.

Yes, running "make install" installs the file by default.

>Now, checking a tarball for sh-utils 2.0j straight off alpha.gnu.org, I
>see no reference whatsoever to charset.alias in either configure or
>intl/Makefile.in.

The charset.alias is created during compilation be an sed script so
you won't see it actually listed in the tarball.

>> > 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?).
>
>Not more so than they do now (except if they normally use WinZip with
>the 'overwrite without prompting' option enabled).  Plus, once it's
>read-only, future versions of gettext/libintl won't be able to update it
>either.

Or we could hack the makefile to prevent installation of charset.alias if
present, can't we?