Eric Wilhelm wrote:
I was thinking it would be a good idea to list outdated CPAN(PLUS) as conflicts using '>=' versions in META.yml. Probably by default.

  http://module-build.sourceforge.net/META-spec-current.html#conflicts

I disagree.

Conflicts implies a fatal package clash for this one specific module.

If CPAN(PLUS) is fatally out of date for a significant subset of CPAN, we need to deal with that seperately, without duplicate a ton of metadata in the META.yml.

Also, CPAN(PLUS) is (should be) entirely outside the concern of the configuration script/phase.

The CPAN client is a layer ABOVE the configure script.

Adam K

Reply via email to