in reply to Re: Removing Modules
in thread Removing Modules

I can think of a few reasons:

You:

I'm sure there are many other possibilities.

--f

Replies are listed 'Best First'.
Re: Re: Re: Removing Modules
by Fastolfe (Vicar) on Feb 02, 2001 at 22:48 UTC
    Perhaps this is just a matter of different backgrounds, but most of these reasons aren't sufficient to cause me to want to run through and remove modules from my system. I guess I see the point though.

    Find you're not using it any more and want to reclaim the disk space

    All 10k? Disk space is cheap. :)
    Decide to save some money, convert from Oracle to PostGres, no longer need DBI::Oracle
    Even working under the assumption that a migration has been 100% completed, there's still the possibility that scripts might want to interact with an Oracle database somewhere at some point of the future.
    Install what looks to be a , only to discover that it's out of date.
    Upgrade it. Perhaps something was lost in this sentence?
    I'm not trying to rebut your points. Each of them are perfectly valid reasons I suppose for someone needing to delete a module from their system. I just don't think any of them are strong enough reasons for me to do it. At any rate, the 'find' command I noticed should suffice in locating the files used by a particular module, and assuming it doesn't break any dependencies, it's probably safe to use that to nuke them. It should also be sufficiently thorough, given the naming schemes we use for files and directories here.
[reply]

In Section Seekers of Perl Wisdom