in reply to Re^4: How do you audit what Perl modules you use?
in thread How do you audit what Perl modules you use?
Good question -- I don't know. I've abandoned PAR and I'm currently looking at Module::Dependency::Indexer as suggested by this node. It did mean I had to install a bunch of CPAN modules, and except for one pesky test that failed, the script at that location now compiles on my system.
- I installed Module::Dependency::Indexer but it found that it needed GD, so I agreed with CPAN and said it could get that too.
- CPAN asked me if libgd was installed in /usr/lib so I went and had a look and discovered that a) no it wasn't and b) I didn't have an RPM for that.
- I downloaded and built libgd from here, and tried to continue the previous installation, but it failed.
- Starting again, I tried to install Module::Dependency::Indexer but of course because of previous errors it failed, so I tried to install GD, but that failed too.
- OK, so I had to do some cleanup, and I did a clean GD followed by a make GD, and that worked.
- I had to do a clean Module::Dependency::Indexer and then make Module::Dependency::Indexer, test Module::Dependency::Indexer (this failed with # t/03indexing.t line 36 is: ok( $i->{'depended_upon_by'}->2 eq 'c' );) and finally force install Module::Dependency::Indexer.
- Are we there yet? No, because compiling the script also required Graph, and that required Heap.
- Wait, there's still more, I also had to install Module::CoreList.
Well, that doesn't happen every day, but for someone new to the language (and the sub-culture), it must be a little daunting.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
|
---|
In Section
Seekers of Perl Wisdom