Re: Re: ExtUtils::Installed and perl5.6.*

Well, what about other than .pm files? Taken Storable as an example, installation consists of 20 (sic!) files and only one of them is .pm, others are: splitted for autoloading subs (.al files and autosplit.ix) and compiled from C (.bs and .so). And it is good enough that all of them are inside Perl hierarchy, sometimes it is not the case.

-- brother ab

Comment on Re: Re: ExtUtils::Installed and perl5.6.*

Replies are listed 'Best First'.
Re: Re: Re: ExtUtils::Installed and perl5.6.* by alien_life_form (Pilgrim) on Oct 19, 2001 at 16:27 UTC
Greetings. Perhaps, if you explained what is the purpose of your endeavour, somebody could come up with a solution. As things are, a combination of what I suggested, plus ExtUtils::Installed::files, plus the knowledge of the (standard) layout of the perl library should get you pretty close to what you're looking for. Cheers, alf	[reply]
Re: Re: Re: Re: ExtUtils::Installed and perl5.6.* by brother ab (Scribe) on Oct 19, 2001 at 16:48 UTC
It is not a secret. I like to try different modules. I am crazy about trying modules because I don't want to reinvent anything :). And at the same time I like to keep my system clean. So I have had a kind of uninstaller for rejected modules. Now it does not work for perl5.6.1 and I'm sad because I need to reinvent this uninstaller ;). And I thought - maybe somebody knows some trick or workaround or something else that could make me happy again :))) -- brother ab	[reply]