in reply to Re: MakeMaker/Module::Build force make install
in thread MakeMaker/Module::Build force make install

Hmm ... there doesn't seem to be an uninstall target with Makefiles created by Module::Build:

make uninstall make: don't know how to make uninstall. Stop
ExtUtils::MakeMaker, on the other hand, supports uninstall.

Oh, and touching the source doesn't trick make install into installing unchanged targets either:

Skipping /foo/bar/baz/Module.pm (unchanged)
Turns out that ExtUtils::Install checks the size and then calls compare of File::Compare which compares the content:
if ( -f $targetfile && -s _ == $size) { # We have a good chance, we can skip this one $diff = compare($sourcefile, $targetfile); }

Replies are listed 'Best First'.
Re^3: MakeMaker/Module::Build force make install
by PodMaster (Abbot) on Mar 11, 2005 at 02:45 UTC
    ExtUtils::MakeMaker, on the other hand, supports uninstall
    But doesn't actually remove the files (at least on win32, this might be platform dependent behavior).

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

Re^3: MakeMaker/Module::Build force make install
by Tanktalus (Canon) on Mar 11, 2005 at 14:06 UTC

    As for the comparing - this is what I call "the computer being too smart." It gets in the way of advanced users who know what they're doing. You may need to add your own target to your makefile which does what you want - largely defeating the entire purpose of a generalised Makefile maker.