in reply to tracking module usage, and abandoning them

I haven't seen anything too fancy for keeping track of module usage. If the OS keeps track of it in the file system you might be able to scoop off a last accessed date and roll your own.

Where I am working basically we all go through one person for module instalation. Otherwise you have to play with the modules in your own user space. It keeps things pretty clean, and if something breaks you know who to go bug :)

Personally though I don't see what the big deal of removing modules would be, and it may be a little dangerous to just go remove them even if they hadn't been used in a few months. Who's to say that somebody didn't bury a use command in an if statement and it just hadn't been called yet.

I guess I don't see the harm in keeping a few extra megs worth of unused modules around myself.

  • Comment on Re: tracking module usage, and abandoning them

Replies are listed 'Best First'.
Re: Re: tracking module usage, and abandoning them
by marius (Hermit) on Feb 20, 2001 at 20:33 UTC
    If you're on a Unix system, you should be able to use the atime flag on find. However, by checking the CPAN reinstall recommendations, you just accessed all those files, so they'll have short atimes even if they've been abandoned for quite some time.

    -marius