But wouldn't that depend on how they "installed" the module? ("Bad developers, bad! Don't copy those files into the directory structure.")
I did look at the file, and it contains more entries, so you certainly have helped me get further along. | [reply] |
Kinda (btw, searching for the .pm files under the @INC folders really is enough).
I refuse to install any module without ExtUtils::MakeMaker, even if I have to write a Makefile.PL
myself (i do it for modules I release here on perlmonks), and so should you.
Why?
Precisely because I like my perllocal.pod's updated when I add modules.
I also like my .packlist's properly maintained,
so I know exactly what came with each distribution I installed (by using ExtUtils::Installed).
PPM does it, and so should every module installing mechanism ;)
It is also one more reason I don't use Module::Build, because as of yet,
it doesn't modify the two perllocal.pod (it's on the TODO list).
You should also check out Module::Corelist, ActiveState may add a bit more modules to their core, but Module::Corelist is still useful nonetheless.
Also, Module::ScanDeps may be of interest to you.
update: I forgot to mention to beware of software which deletes/overwrites your perllocal.pod
(like Everything).
MJD says you
can't just make shit up and expect the computer to know what you mean, retardo!
I run a Win32 PPM
repository for perl 5.6x+5.8x. I take requests.
** The Third rule of perl club is a statement of fact: pod is sexy.
|
| [reply] |