On Aug 5, 2006, at 4:27 AM, Johan Vromans wrote:
If Test::Ridiculous were not installed, I could chase down the perl
installation to find out what files were added[2], and distribute
these to the production systems. Now I have to manually weed out the
files that are not needed for production.
[...]
[2] Module::Build at least provides a target fakeinstall that will
provide this information. Unfortunately, most modules are still
MakeMaker based.
A trivial patch to MakeMaker would let you do this with MakeMaker
too, since it's just a pass-through to ExtUtils::Install that's doing
the real work.
Essentially the Makefile would need this change:
--- Makefile~ 2006-08-03 22:10:19.000000000 -0500
+++ Makefile 2006-08-05 12:45:26.000000000 -0500
@@ -215,7 +215,8 @@
ECHO_N = echo -n
UNINST = 0
VERBINST = 0
-MOD_INSTALL = $(PERLRUN) -MExtUtils::Install -e 'install([EMAIL PROTECTED],
'\''$(VERBINST)'\'', 0, '\''$(UNINST)'\'');'
+NONONO = 0
+MOD_INSTALL = $(PERLRUN) -MExtUtils::Install -e 'install([EMAIL PROTECTED],
'\''$(VERBINST)'\'', $(NONONO), '\''$(UNINST)'\'');'
DOC_INSTALL = $(PERLRUN) "-MExtUtils::Command::MM" -e perllocal_install
UNINSTALL = $(PERLRUN) "-MExtUtils::Command::MM" -e uninstall
WARN_IF_OLD_PACKLIST = $(PERLRUN) "-MExtUtils::Command::MM" -e
warn_if_old_packlist
and then you'd run:
% make pure_install NONONO=1
That wouldn't show you the man page installs, but in an environment
like the one you're describing maybe you don't care about man pages
anyway?
-Ken
