Message-ID: <3634695E.FB5CBD0E@gmx.net> Date: Mon, 26 Oct 1998 11:21:50 -0100 From: Robert Hoehne Organization: none provided X-Mailer: Mozilla 4.01 [de] (Win95; I) MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: proposed change to autoconf macro X-Priority: 3 (Normal) References: <36337C92 DOT 5840A031 AT montana DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com bowman wrote : > > Using autoconf, as an example, if one just downloads acnf212b.zip, as > many people > do who have no interest in the sources, all there is is 'readme.djg' > which references > Robert Hoehne as the person who did the dj port. The source zip does > have ChangeLog and > ChangeLog.1, but these are the original GNU authors and maintainers. This was my fault not to include the original readme and other related readme's in the binary acbf212b.zip > OK, in this instance, I see two different areas. First, in the binary > djgpp package, there > is the acoldnames.m4 that has been truncated to acoldname.m4. BTW, This is really a bug only related to the DJGPP port and should be reported only to the DJGPP people, either to the person who made the port for DJGPP available (in this case me) or/and to the djgpp-workers list. > This problem would seem to be specific to that one file, but it > obviously needs to be > cleaned up on all the simtel mirrors, etc. If one sees something like If the package is reuploade to DJ's site, and he places it on simtel.net it will be automatically updated on all simtel.net mirrors after some time. > an appropriate person to contact, or is just posting to djgpp-workers > suffiecient? In general this should be enough, since in most cases the person, who made such a package for DJGPP availaible, reads this list or the others knows about the correct person(s). > as a valid root is DOS specific, and of primary interest to the djgpp > community, but it > would be of interest to anyone porting autoconf to Cygwin, MinWg32, or > anything with > an underlying DOS filesystem, perhaps even the UMSDOS Linux variants. Any GNU package contain many system-specific things, which are of interest for only some systems and not the others. So why should DJGPP an exception by not sending DJGPP-specific patches the GNU mainatainer? If the patches will work for DJGPP (your responsibility) and will not break any other system, you can be nearly sure, that your patches will be applied. Robert -- ****************************************************** * email: Robert Hoehne * * Post: Am Berg 3, D-09573 Dittmannsdorf, Germany * * WWW: http://www.tu-chemnitz.de/~sho/rho * ******************************************************