|laziness, impatience, and hubris|
How do you audit what Perl modules you use?by talexb (Canon)
|on May 09, 2005 at 17:13 UTC||Need Help??|
talexb has asked for the
wisdom of the Perl Monks concerning the following question:
The company I work for is getting ready to roll out some servers installed with our software, and it's my job to track down which modules we use and what copyrights and licenses apply to each module.
Is there any tool that exists to track down what modules a web application uses? I can imagine writing something simple (heh) that has a look at what modules are used in our modules and scripts and following that back to CPAN, but as usual I'm thinking about the meta-issue, because I'm going to want to do this again for this project, and in future for other projects.
And, as we're developing on RedHat 9 system, I need to do a similar dependency thing on the various RPMs that I've used, along with cases like A -> (depends on) B, B -> C, C-> D, D -> E but don't worry about E, we'll just install D with nodeps it'll be OK, trust me ..
I need to document that as well -- I'll probably use our Wiki, but it would be neater if I could put it into a database.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds