From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: ANNOUNCE: DJGPP port of Gawk 3.0.4 uploaded Date: Sat, 22 Jan 2000 09:24:00 +0200 Organization: NetVision Israel Lines: 13 Message-ID: <38895B10.300F5999@is.elta.co.il> References: <200001211327 DOT HAA15130 AT darwin DOT sfbr DOT org> NNTP-Posting-Host: ras1-p17.rvt.netvision.net.il Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.netvision.net.il 948525838 18826 62.0.172.19 (22 Jan 2000 07:23:58 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 22 Jan 2000 07:23:58 GMT X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,ru,hebrew To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Jeff Williams wrote: > > Is there a reason to (or not to) also include the symlink `nawk.exe' as > well as `awk.exe' (both stubedited to point to gawk)? The reason `awk.exe' is included is because the "install:" target of the Gawk Makefile creates that symlink. It does no such thing for `nawk'. In general, it is my opinion that a port should faithfully do what the original distribution does, no more, no less. However, if adding `nawk' would help, it shouldn't be a problem to do that. But I wonder if the reason for doing so might be valid for other platforms as well, in which case I suggest to report this to the Gawk maintainer.