Mail Archives: djgpp-workers/2001/03/04/09:14:41
> Can I assume that a non-MZ file is a batch file in the outer else clause?
I don't think so, unless the if statement is only used if -m is passed a
mode with an executable bit set.
Otherwise
ginstall ABOUT-NLS /dev/env/DJDIR/share/locale/ABOUT-NLS
would create ABOUT-NLS.bat, wouldn't it?
Even preserving the original extension for such cases might not be a good
idea; consider
ginstall somefile.install /dev/env/DJDIR/share/whatever/somefile
You want 'somefile', not 'somefile.install' to be created. I think you
really should limit the deductions to stubbed DJGPP executables. True
DOS packages (as opposed to ported Unixy stuff) who may need to install
other types of .exe files, or .com and .bat files will need to use ginstall
properly (ie 'ginstall foo.com <dir>' or 'ginstall foo.com <dir>/foo.com').
I expect the fix is mainly needed for automake and friends, so when they
build 'program' as main target, they can install 'program' and ginstall
will make sure this arrives as 'program.exe' if applicable. Then again,
AC_EXEEXT should really be added to configure.in when porting to DOS
(but then you hit the 'DJGPP maintainers shouldn't need autoconf/automake'
axiom again).
> finished working on ginstall, I'll test dd, SFN builds and then I think
> Fileutils 4.0 port is ready for a beta. Please note that I'm targetting
> building with DJGPP 2.03. I think using DJGPP CVS's new goodies will be
> quite some work.
FYI, a new fileutils should be released soon (its release is being delayed
mainly because the maintainers are waiting for autoconf 2.50 to be
released).
- Raw text -