> On 5/28/05, Autrijus Tang <[EMAIL PROTECTED]> wrote: > > On Sat, May 28, 2005 at 09:24:13PM +0200, Gregoire Pean wrote: > > > "make install" with Pugs creates a pugs.exe.bat file in Perl bin > > > directrory, which is useless and don't work since > pugs.exe is not a > > > Perl script. It should be removed. > > > > Thanks -- it seems that some EXE_FILES hackery is needed in > Makefile.PL. > > Would you like to investigate a patch?
I looked at this today, and found out that it's probably ExtUtils::MakeMaker's misbehaviour, or pl2bat, or both. Pugs differs compared to any other Perl module by creating an executable that relies on Perl. Usually modules are other way round: they are used from Perl. ExtUtils::MakeMaker for every "script" runs "FIXIN" which means pl2bat on Win32, and no-one expects that to be binary executable. This may be fixed on Perl side? Or better copy "pugs.exe" with a different approach (but I suspect this is not ideal) Additionally, following lines in Makefile.PL bother me a bit: pure_vendor_install :: \$(NOECHO) \$(MOD_INSTALL) \\ \$(INST6_LIB) \$(DESTDIR)$config->{privlib} \\ \$(INST6_ARCHLIB) \$(DESTDIR)$config->{archlib} \\ \$(INST6_BIN) \$(DESTDIR)$config->{installbin} \\ \$(INST6_SCRIPT) \$(DESTDIR)$config->{installscript} \\ \$(INST6_MAN1DIR) \$(DESTDIR)$config->{installman1dir} \\ \$(INST6_MAN3DIR) \$(DESTDIR)$config->{installman3dir} What if $config->{installman1dir} is empty string? And this is the case! So it appears that "install" tries to copy from \$(INST6_MAN1DIR) to \$(INST6_MAN3DIR) There's no damage, as those are empty sets, but looking forward no-one knows what will be... Should doublequotes suffice? Advices? Best regards, Vadim.