http://www.perlmonks.org?node_id=998801


in reply to Re^2: "deinistall" DateTime
in thread "deinistall" DateTime

If you want to uninstall all of the dependencies that got installed when you tried to install DateTime, then yes, you just delete the files that were installed. Just be careful not to delete anything that existed before you tried to install the library.

Though IMO, I don't think it hurts to have a few extra libraries installed (unless you're talking Switch).

Replies are listed 'Best First'.
Re^4: "deinistall" DateTime
by bart (Canon) on Oct 13, 2012 at 00:58 UTC
    There are some tricks one could use the see what modules are installed most recently.

    You can check the "ctime" of those module files. Unless you did something funky to your filesystem, this should be quite a reliable source for candidate modules to uninstall.

    And perldoc perllocal lists the contents of perllocal.pod, which ought to be updated with new module additions, including date of installation, with every installation using CPAN, and hopefully, with replacements of CPAN, too. (I think I recall that that PPM, (originally) ActiveState's alternative module installer for Windows, doesn't update it.)

[reply]
[d/l]
[select]

      (I think I recall that that PPM, (originally) ActiveState's alternative module installer for Windows, doesn't update it.)

      I do recall that PPM keeps track itself, in a ppm.xml somewhere in @INC

[reply]
Re^4: "deinistall" DateTime
by dhofmeister (Initiate) on Oct 15, 2012 at 17:15 UTC

    Simply rm'ing the DateTime/ subdirectory appears to have done the trick. Since the dependencies for DateTime seem to have installed ok, i didn't bother (nor want) to delete them.

    the version control suggestion is a good idea, imo. too bad it's not set up on my system :-)

[reply]

In Section Seekers of Perl Wisdom