SCIENTIFIC-LINUX-USERS Archives

December 2007

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
John Summerfield <[log in to unmask]>
Reply To:
John Summerfield <[log in to unmask]>
Date:
Tue, 4 Dec 2007 05:50:56 +0900
Content-Type:
text/plain
Parts/Attachments:
text/plain (51 lines)
Michael Mansour wrote:
> Hi,
> 
> I have a couple of perl modules of the same name installed in my OS. This is
> expected as I've hand compiled various apps.
> 
> What I'd like to know is, how I'd determine which perl module is actually used?
> 
> As an example, I have the Base64.pm in three locations - please don't ask why
> :), and when I run:
> 
> # perl -MMIME::Base64 -e '{print "$MIME::Base64::VERSION\n"}'
> 3.07
> 
> Yet I do not know which one it's picking up, as I have one from Sep 20  2004,
> another from Nov 30  2005 and another from this year Jun 15 01:35.
> 
> I know perl searches through paths in its environment (not sure where it gets
> that from), but any ideas how I can find out which Base64.pm is being used?
Plan the first:
To each of then,
chmod 000

then (as not-root) confirm the above doesn't work.
Restore one to previous permissions, repeat test until it works.

Plan the second
strace -f -o /tmp/trace \
   perl -MMIME::Base64 -e '{print "$MIME::Base64::VERSION\n"}'
fgrep Base64.pm /tmp/trace

Finally, discuss with your suppliers asking why the package their 
software this way, instead of saying "it requires example.pm, available 
from CPAN, and included in all the best distros."



-- 

Cheers
John

-- spambait
[log in to unmask]  [log in to unmask]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)

ATOM RSS1 RSS2