[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: on using `makeinfo --no-split' to solve filename conflicts
From: |
Richard Dawe |
Subject: |
Re: on using `makeinfo --no-split' to solve filename conflicts |
Date: |
Mon, 17 Feb 2003 23:24:52 +0000 |
Hello.
Zaretskii Eli wrote:
[snip]
> > From: Alexandre Duret-Lutz [mailto:address@hidden
> > Sent: Friday, February 14, 2003 10:40 PM
> >
> > >> What else could I do so these files do not conflict on system
> > >> like DJGPP, with 8+3 filenames?
> >
> > Zaretskii> When `makeinfo' runs on a 8+3 filesystem, it automatically
> > Zaretskii> produces automake.i1, automake.i2, etc. instead
> > of automake.info-*
> > Zaretskii> files. If you need to do this on Windows, set
> > LFN=n in the
> > Zaretskii> environment before running `makeinfo'.
> >
> > Ok, but I'm not really concerned by what the DJGPP port of
> > makeinfo does when it runs [*], since most autoconfiscated
> > projects ship with info files already built.
> >
> > For instance
> > ftp://sources.redhat.com/pub/automake/automake-1.7.2b.tar.gz
> > comes with automake.info, automake.info-1, automake.info-2, etc.
> >
> > What happens when you unpack this tarball? Does tar
> > automatically renames these files?
>
> If you unpack with DJTAR, a program supplied with DJGPP, it will
> indeed rename the files.
[snip]
Unless I'm mistaken: For automatic renaming don't we need to point djtar at a
mapping file for the filenames (conventionally called fnchange.lst). Otherwise
djtar will prompt the user for the new filename(s).
IMHO the automake info docs should be generated using --no-split.
Thanks, bye, Rich =]
--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]