Harry Putnam <[EMAIL PROTECTED]> writes:
> I've stumbled around with this before and someone posted something
> that came close but still doesn't quite do what I want.
>
> Maybe it isn't important enough to get this involved with it.
>
> Here is the problem:
>
> Summary run home made tools against only the uniq paths that might contain
> perl *.pm files.
>
> In my case:
> $ perl -e 'print $newINC = join("\n",@INC),"\n";'
> /usr/local/lib/perl5/5.8.0/i686-linux
> /usr/local/lib/perl5/5.8.0
> /usr/local/lib/perl5/site_perl/5.8.0/i686-linux
> /usr/local/lib/perl5/site_perl/5.8.0
> /usr/local/lib/perl5/site_perl
> /usr/lib/perl5/5.6.1
> /usr/lib/perl5/site_perl/5.6.1
> /usr/lib/perl5/site_perl
> /usr/lib/perl5/Text
> /usr/lib/perl5/vendor_perl/5.6.1
> /usr/lib/perl5/vendor_perl
> /usr/lib/perl5/5.6.1/i386-linux
> /usr/lib/perl5/site_perl/5.6.1/i386-linux
> /usr/lib/perl5/vendor_perl/5.6.1/i386-linux
Very strange but some how that message got curtailed. I'm not sure
what happened to it.
The rest of it said something like:
I want to pull out only the uniq paths from @INC programmatically.
Maybe its not a big deal but running my tools against all the paths
above seems like it really wastes energy. Maybe perl doesn't care..
I'm on a P4 with 512mb ram.
One way would be to just run all *.pm hits into a hash and only the
uniq ones would survive. Very labor intensive I'd think.
Its easy to spot the base paths by eye:
/usr/local/lib/perl5
/usr/lib/perl5/
On some machines there might be more. But how to kick them out
programmatically?
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
