-
Notifications
You must be signed in to change notification settings - Fork 194
Config module Missing #1374
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
Comments
Config does not exist as a package in the perl release tarball. It is created in the build process. MetaCPAN indexes everything in its static form without building. This is the same issue as metacpan/metacpan-web#2587, and several other issues linked to that one. |
Metacpan is only able to index files from the source tarball, not generated modules like Config; this means a lot of core documentation is only available at perldoc.perl.org or with the local perldoc utility. You can use Module::CoreList to determine core module status for various versions of Perl. |
It doesn't look like Module::CoreList distinguishes between dual-life and non-dual-life modules distributed with core. I'd like to ignore non-dual-life modules but pick up changes from dual-life modules. |
I added a line to skip |
If you check the upstream configuration, upstream cpan means it is for sure dual life, upstream blead you can then consult metacpan (or the package index itself) and if the indexed result is not the perl distribution it is dual life. |
The |
You would need to do the index check for anything not listed as cpan regardless, it would just remove the question for those modules listed. For Config as noted, it is not indexed as a package as PAUSE also does not see it, so since it is also not listed as upstream cpan, it can be assumed to not be dual life. |
Yes, I'm just ignoring Config, which fixes my issue. |
I assume something changed with core-only modules and I missed it, but I discovered that this URL, which AFAIK used to work, now returns a 404:
https://fastapi.metacpan.org/v1/module/Config
Do I need to do something to figure out which in-core (non-dual-life) modules to skip in my app?
The text was updated successfully, but these errors were encountered: