[
https://issues.apache.org/jira/browse/LUCY-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15545375#comment-15545375
]
Nick Wellnhofer commented on LUCY-313:
--------------------------------------
Since version 0.40_11, Module::Build doesn't add the {{provides}} section if
the {{no_index}} property is set (directly, no in {{meta_add}}). Maybe we
should simply add a {{no_index}} entry like:
{noformat}
no_index => {
directory => [qw( buildlib )],
package => [qw( Lucy::Test ... )],
},
{noformat}
I'm not sure what the module lists in {{buildlib/Lucy/Redacted.pm}} are about,
but it seems that in order to disable indexing of private or obsolete packages,
we should either
- remove the corresponding {{.pm}} files, or
- add the package name to {{no_index}}.
> 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)
