Skip Menu |

This queue is for tickets about the Dist-Zilla-Plugin-Test-ReportMetadata CPAN distribution.

Report information
The Basics
Id: 107449
Status: resolved
Priority: 0/
Queue: Dist-Zilla-Plugin-Test-ReportMetadata
People
Owner: Support [...] RoxSoft.co.uk
Requestors: ether [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 0.4.1

History Show all quoted text
  Thu Oct 01 12:33:20 2015 ether [...] cpan.org - Ticket created
Subject: why Module::Metadata?
Your documentation explains that you cloned [Test::ReportPrereqs] but replaced the use of MM->parse_version with Module::Metadata, but doesn't explain why? as a member of the toolchain gang, and one of the (current) primary maintainers of Module::Metadata, is there something I should know? (FWIW, it's been the intent for quite a while that MM->parse_version will replace its own implementation with Module::Metadata; we're just not quite there yet with covering all the usecases adequately yet.)
  Thu Oct 01 14:46:12 2015 Support [...] RoxSoft.co.uk - Correspondence added
Subject: Why Module::Metadata?
On Thu Oct 01 12:33:20 2015, ETHER wrote: Show quoted text
> Your documentation explains that you cloned [Test::ReportPrereqs] but > replaced the use of MM->parse_version with Module::Metadata, but > doesn't explain why?
From the documentation "If you are using Module::Build then Module::Metadata is already a dependency" Since I use MB not EUMM I'm using Module::Metadata for the version parsing since it's already available. I did not want a metadata report generator to pull in EUMM just to do version parsing
  Thu Oct 01 14:46:12 2015 The RT System itself - Status changed from 'new' to 'open'
  Thu Oct 01 14:46:12 2015 Support [...] RoxSoft.co.uk - Taken
  Thu Oct 01 14:46:13 2015 Support [...] RoxSoft.co.uk - Fixed in 0.4.1 added
  Thu Oct 01 14:54:39 2015 ether [...] cpan.org - Correspondence added
On 2015-10-01 11:46:12, PJFL wrote: Show quoted text
> On Thu Oct 01 12:33:20 2015, ETHER wrote:
> > Your documentation explains that you cloned [Test::ReportPrereqs] but > > replaced the use of MM->parse_version with Module::Metadata, but > > doesn't explain why?
> > From the documentation > > "If you are using Module::Build then Module::Metadata > is already a dependency" > > Since I use MB not EUMM I'm using Module::Metadata for the version > parsing since it's already available. I did not want a metadata > report generator to pull in EUMM just to do version parsing
When you say "pull in", do you mean as a dependency, or load it into the runtime environment? For the perl process running the test, neither ExtUtils::MakeMaker nor Module::Metadata would be loaded yet, regardless... so either way the thing doing the version parsing needs to be loaded. For prerequisites.. you do realize that both ExtUtils::MakeMaker and Module::Metadata are core modules? I'm just trying to understand your motivation here, and what you're trying to optimize for.
  Thu Oct 01 15:10:05 2015 Support [...] RoxSoft.co.uk - Correspondence added
On Thu Oct 01 14:54:39 2015, ETHER wrote: Show quoted text
> When you say "pull in", do you mean as a dependency
Yes. I do not want to specify EUMM as dependency
  Thu Oct 01 15:10:06 2015 Support [...] RoxSoft.co.uk - Status changed from 'open' to 'resolved'