Document about OS-packaged modules vs docker-perl
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 129
- Forks
- 54
- Avg merge
- 21m
- Merged PRs (30d)
- 2
Description
Debian Perl packages are not guaranteed to work (much more even detected) against the Perl we build here, especially as these perls might not even have the same version and @INC paths...
Let me prepare a PR on docker-library/docs for this, also the salient points are in https://github.com/Perl/docker-perl/issues/26#issuecomment-515648439
Originally posted by @zakame in https://github.com/Perl/docker-perl/issues/92#issuecomment-701916887
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the documentation repository at docker-library/docs and the salient points in Perl/docker-perl#26 comment 515648439. Document that Debian OS-packaged Perl modules are not guaranteed to work with the Perl built in these images, including differences in Perl versions and @INC paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, perl
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100