X-Authentication-Warning: new-smtp2.ihug.com.au: Host p27-max12.syd.ihug.com.au [203.173.155.155] claimed to be acceleron Message-ID: <004901c144fd$2d93f350$0a02a8c0@acceleron> From: "Andrew Cottrell" To: "Eli Zaretskii" Cc: References: Subject: Re: which crashes Date: Mon, 24 Sep 2001 23:31:11 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Reply-To: djgpp-workers AT delorie DOT com > > I checked out the differences between Which 2.11 and 2.12 and the changes > > are with the man pages only. I couldn't see who produced the DJGPP port as > > it has allot of DJGPP changes compared to the original which.c source. > > I have a few more complaints about the ported Which. For example, > there's no DJGPP-specific README anywhere in sight, and it looks like a > user is supposed to run "sh ./configure" to configure the package. These > things shouldn't be left without saying them explicitly. > > > The next time I build the Which package for testing under WIn 2K should I > > include these changes? > > I don't see any sense in producing a binary that is known to bomb... > > > I can also produce a source package as well. > > Any binary distribution should be accompanied by a source distribution. > If you produce the binary from modified sources, you should make those > modified sources available as well. That's a GPL requirement. If no one does it before me I will add this to me list of work to be done. I will produce a Which source and binary release for Win 2K testing and then normalise the packages to be more like the normal DJGPP packages and while I am at it I should update it to 2.12. If any one else wants to do this or starts this first could you please let me know so I do not waste my time. Thanks, Andrew