[karl@gnu.org: [texinfo-pretest] texinfo 4.7.91 pretest available]

[Juan Manuel Guerrero]

Datum:		Fri, 17 Dec 2004 11:22:55 +0100
Von:			Stepan Kasal <kasal at ucw.cz>
An:			Juan Manuel Guerrero <st001906 at hrz1.hrz.tu-darmstadt.de>
Kopie an:		djgpp-workers at delorie.com, texinfo-pretest at texinfo.org
Betreff:		Re: [karl at gnu.org: [texinfo-pretest] texinfo 4.7.91 pretest available]
> Hi,
> 
> On Thu, Dec 16, 2004 at 09:17:27PM +0200, Juan Manuel Guerrero wrote:
> > INTTYPES.M4    : texinfo-4.7.91/m4/inttypes-pri.m4
> > 		                texinfo-4.7.91/m4/inttypes.m4
> > 		                texinfo-4.7.91/m4/inttypes_h.m4
> > ONCEONLY.M4    : texinfo-4.7.91/m4/onceonly.m4
> > 		                   texinfo-4.7.91/m4/onceonly_2_57.m4
> ...
> > of /djgpp/config.sed to fix the makefiles for the new names.
> 
> these files are only referrenced from aclocal.m4 .  Thusly:
> - you can let it be, it won't cause problems unless someone runs autoconf
> - you can patch aclocal.m4
> - you can re-run aclocal
> 
> (Well, they are also listed in EXTRA_DIST variable in m4/Makefile.am.
> But who would do ``make dist'' with texinfo in djgpp?)

No djgpp user should run "make dist" at all. If he does he will certainly get
no support from me ;-).
Neitherless the difficulty remains that the official FSF texinfo source
package can not be decompressed on plain dos nor on Win32 if long file name
support is not available.
IMHO there are three possible approches to solve this issue:
1) We do not care about it. In this case, our tar utility will ask for a new
   name during the extraction process if it can not create one of the files.
   Because those files are not checked dependencies during the compilation
   process, the compilation process will succesfuly finish even if those files
   have been extracted with a different name or not extracted at all.
2) Our tar utility is capable to rename files during extraction looking at a
   translation list. In this case we must supply such a list, lets call it
   "djgpp/fnchange.lst". The user will be able to extract this file and use it
   to rename the conflicting files on the fly during extraction.
3) We do not care and let the maintainer of the djgpp packages (txi4NN[bsd].zip)
   take care about all this.
Please note that I have told all this only for your information. The texinfo
people should not worry about all this. This is a really minor djgpp specific
issue that should not be discussed here. If I get no response from the djgpp
workers I will assume the first case and the issue wil be finished.

Regards,
Juan Mnauel Guerrero