Skip Menu |

This queue is for tickets about the Moose CPAN distribution.

Report information
The Basics
Id: 128235
Status: open
Priority: 0/
Queue: Moose
People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: 2.2011
Fixed in: (no value)

History Show all quoted text
  Sun Jan 13 04:59:20 2019 ANDK [...] cpan.org - Ticket created
Subject: Moose/Conflicts.pm missing in META.yml
As per subject. Maybe it is a Dist::Zilla bug, I don't know, but I have verified that Moose does install Moose/Conflicts.pm but does not declare it in `provides`. What do you think, what needs fixing?
  Sun Jan 13 13:22:24 2019 ether [...] cpan.org - Correspondence added
On 2019-01-13 01:59:20, ANDK wrote: Show quoted text
> As per subject. Maybe it is a Dist::Zilla bug, I don't know, but I > have verified that Moose does install Moose/Conflicts.pm but does not > declare it in `provides`. > > What do you think, what needs fixing?
Yes, it looks like it's due to the order of the plugins, where the Conflicts module is generated after the 'provides' metadata has been calculated. I'm not sure if it's an issue though -- Moose::Conflicts isn't in 02packages.details.txt, but does it need to be? I can't think of a situation where a distribution would need to declare a prerequisite on this module in particular, as it's just supporting code for conflict resolution during other modules' installation. I'll think about it more as we gear up for another Moose release (which might be soon).
  Sun Jan 13 13:22:25 2019 The RT System itself - Status changed from 'new' to 'open'
  Sun Jan 13 16:22:48 2019 ANDK [...] cpan.org - Correspondence added
There is no urgent need around. I discovered the discrepancy while trying some potential new options out on CPAN.pm and one of those found the missing declaration. But in the grand scheme of things, it wouldn't be wrong when the index developed a bit closer to the truth.