[ 
https://issues.apache.org/jira/browse/LUCY-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15716048#comment-15716048
 ] 

Nick Wellnhofer commented on LUCY-313:
--------------------------------------

I started with a manual {{no_index}} section but kept the {{.pm}} files for 
private classes for now:

https://git1-us-west.apache.org/repos/asf?p=lucy.git;a=commitdiff;h=710159091b19149088cc77147006730f31931a25

I also found a good explanation of what the {{provides}} section actually does:

{quote}
"provides" in metadata is a hint to the PAUSE indexer as to what modules are 
inside the distribution that are eligible for indexing. (It's not a required 
field, but might be in v3.) When it exists, it is the _authoritative_ source 
for what to index -- if an otherwise-eligible module is not listed (i.e the 
dist upload is authorized, etc), it is left out of the index.
-- Karen Etheridge https://github.com/metacpan/metacpan-web/issues/1152
{quote}

So "provides" is a whitelist, and "no_index" (without "provides") is a 
blacklist. This is not to be confused with the "Provides" section on MetaCPAN 
which is something else altogether.

The only effect of my commit is that {{Lucy::Test}} isn't indexed by CPAN 
anymore. If we want to deindex private classes, we have to add them to 
{{no_index}} or start to generate a {{provides}} section listing only public 
classes.

> Rework PAUSE exclusions
> -----------------------
>
>                 Key: LUCY-313
>                 URL: https://issues.apache.org/jira/browse/LUCY-313
>             Project: Lucy
>          Issue Type: Bug
>            Reporter: Nick Wellnhofer
>
> There's some code in Build.pm that creates a list of files that are added to 
> the {{no_index}} entry in {{META.json}}. But Module::Build also creates a 
> {{provides}} entry containing {{.pm}} files found in {{lib}} which seems to 
> override the {{no_index}} files. Anyhow, all these files appear on 
> search.cpan.org and in 02packages.details.txt.
> I'm not sure what the original intention was, but it looks like it doesn't 
> work as intended or as it used to.
> The {{no_index}} entry also contains lost of unrelated file types like {{.c}} 
> or {{.cfh}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to