Skip Menu |

This queue is for tickets about the dmake CPAN distribution.

Report information
The Basics
Id: 95273
Status: resolved
Priority: 0/
Queue: dmake
People
Owner: Nobody in particular
Requestors: CHORNY [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Normal
Broken in: 4.12.2.2
Fixed in: (no value)

History Show all quoted text
  Fri May 02 08:13:00 2014 CHORNY [...] cpan.org - Ticket created
Subject: incorrect META.yml
provides: dmake: file: META.yml means that there is "package dmake" in META.yml. "provides This describes all packages provided by this distribution. This information is used by distribution and automation mechanisms like PAUSE, CPAN, metacpan.org and search.cpan.org to build indexes saying in which distribution various packages can be found. The keys of provides are package names that can be found within the distribution. " So provides should be empty. Otherwise this distribution is indexed in module list. -- Alexandr Ciornii, http://chorny.net
  Fri May 02 13:15:09 2014 shay [...] cpan.org - Correspondence added
On Fri May 02 08:13:00 2014, CHORNY wrote: Show quoted text
> provides: > dmake: > file: META.yml > > means that there is "package dmake" in META.yml. > "provides > This describes all packages provided by this distribution. This > information is used by distribution and automation mechanisms like > PAUSE, CPAN, metacpan.org and search.cpan.org to build indexes saying > in which distribution various packages can be found. > > The keys of provides are package names that can be found within the > distribution. > " > > So provides should be empty. Otherwise this distribution is indexed in > module list.
Hmmm. This was done at the suggestion of PAUSE indexer gurus after my previous release (without such a "provides" section) failed to index. See this ticket: https://github.com/andk/pause/issues/110 In particular, Dave Golden wrote: "I believe in Lancaster we agreed that the 'file' has to be the "source" of the namespace claim, not a literal .pm file, and that one could name the META.json file itself if the source of the package claim is purely metadata." It seems that the spec needs updating in line with what David wrote, so is it worth moving this to the CPAN::Meta::Spec queue? David is the maintainer of CPAN::Meta::Spec, so hopefully won't disagree with himself! ;-) Otherwise I need to find some other way to keep the PAUSE indexer happy...
  Fri May 02 13:15:10 2014 The RT System itself - Status changed from 'new' to 'open'
  Sat May 31 14:47:26 2014 shay [...] cpan.org - Correspondence added
On Fri May 02 13:15:09 2014, SHAY wrote: Show quoted text
> It seems that the spec needs updating in line with what David wrote, > so is it worth moving this to the CPAN::Meta::Spec queue? David is the > maintainer of CPAN::Meta::Spec, so hopefully won't disagree with > himself! ;-) Otherwise I need to find some other way to keep the PAUSE > indexer happy...
Now reported here: https://github.com/Perl-Toolchain-Gang/CPAN-Meta/issues/64
  Sat May 31 23:44:40 2014 dagolden [...] cpan.org - Correspondence added
Spec clarified and shipped to CPAN as CPAN-Meta-2.141520 Chorny, this was discussed in Lancaster as part of the Lancaster Consensus. Rather than making people ship dummy .pm files just to claim a namespace, we decided that declaring 'file' to be META.json was sufficient. We actually decided that having 'file' be mandatory was unnecessary, but didn't want to actually change the spec until a broader v3 discussion.
  Sun Jun 01 17:50:33 2014 shay [...] cpan.org - Correspondence added
Now resolved by David's clarification to the CPAN::Meta::Spec. Thank you for raising the issue and thereby causing the spec to be clarified.
  Sun Jun 01 17:50:34 2014 shay [...] cpan.org - Status changed from 'open' to 'resolved'