Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future 2.002002 #6

Merged
merged 3 commits into from Jul 7, 2016
Merged

Future 2.002002 #6

merged 3 commits into from Jul 7, 2016

Conversation

kentfredric
Copy link
Member

No description provided.

This is mostly a failsafe trapping for bad logic and people who misuse
MetaProvides::FromFile

Aims to guard against not only "Bad filename" but "bad Path
convention", but this latter is weakly enforced by "using what dzil
uses".

CPAN::Meta::Spec  says Provides entries must use UNIX conventions
and use paths relative to base.
Presently if you have nested modules, the modules inside may be indexed,
but the package itself can't be "use"'d.

This is not a definte issue, but often when it happens its by accident.
@kentfredric kentfredric self-assigned this Jul 7, 2016
@coveralls
Copy link

coveralls commented Jul 7, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 2a9e822 on future-2.002002 into e2696bc on master.

@kentfredric kentfredric merged commit 2a9e822 into master Jul 7, 2016
@kentfredric kentfredric deleted the future-2.002002 branch July 7, 2016 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants