Skip to content

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

Closed
theory opened this issue Apr 28, 2025 · 8 comments
Closed

Config module Missing #1374

theory opened this issue Apr 28, 2025 · 8 comments

Comments

@theory
Copy link
Contributor

theory commented Apr 28, 2025

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?

@haarg
Copy link
Member

haarg commented Apr 28, 2025

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.

@Grinnz
Copy link
Contributor

Grinnz commented Apr 28, 2025

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.

@theory
Copy link
Contributor Author

theory commented Apr 28, 2025

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.

@theory
Copy link
Contributor Author

theory commented Apr 28, 2025

I added a line to skip Config and that fixes my issue.

@theory theory closed this as completed Apr 28, 2025
@Grinnz
Copy link
Contributor

Grinnz commented Apr 28, 2025

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.

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.

@theory
Copy link
Contributor Author

theory commented Apr 28, 2025

The %upstream hash, despite the docs, contains only cpan values.

@Grinnz
Copy link
Contributor

Grinnz commented Apr 28, 2025

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.

@theory
Copy link
Contributor Author

theory commented Apr 28, 2025

Yes, I'm just ignoring Config, which fixes my issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants