Re^3: Properly expressing module prerequesites for CPAN

The need to imbed the dependancy list in Makefile.PL is why I don't do it now---plus a basic resentment over why I should have to do this in the first place. I'm blindingly clear about the requirements in my docs, that should be enough. Clearly mechanical testing isn't entirely a step forward.

--hsm

"Never try to teach a pig to sing...it wastes your time and it annoys the pig."

Comment on Re^3: Properly expressing module prerequesites for CPAN

Replies are listed 'Best First'.
Re^4: Properly expressing module prerequesites for CPAN by sgifford (Prior) on Jul 09, 2004 at 15:47 UTC
The reason is so that CPAN can detect the dependencies automatically. As brilliant as CPAN is, it still can't parse human language well enough to understand the docs, no matter how blindingly clear they are. :) There are modules to help with this maintenance, like Module::Depends::Intrusive and Module::ScanDeps.	[reply]
Re^4: Properly expressing module prerequesites for CPAN by iburrell (Chaplain) on Jul 09, 2004 at 16:49 UTC
CPAN.pm does not read documentation. I bet most of your users don't read the documentation either. I know I don't read the module docs unless something goes wrong or I need to program with the module. Modules that don't include dependencies are annoying because they require manually reading the docs, and install those modules.	[reply]