https://bugzilla.redhat.com/show_bug.cgi?id=1936241
Bug ID: 1936241 Summary: Compiled @INC in 5.32 No longer Includes Suitable Path For Custom System-Wide Modules Product: Fedora Version: 33 Hardware: All OS: Linux Status: NEW Component: perl Severity: medium Assignee: jplesnik@redhat.com Reporter: claywj@gmail.com QA Contact: extras-qa@fedoraproject.org CC: caillon+fedoraproject@gmail.com, iarnell@gmail.com, jplesnik@redhat.com, kasal@ucw.cz, mmaslano@redhat.com, perl-devel@lists.fedoraproject.org, ppisar@redhat.com, psabata@redhat.com, rhughes@redhat.com, sandmann@redhat.com, spotrh@gmail.com Target Milestone: --- Classification: Fedora
Description of problem:
Removing /usr/local/share/perl5 for the version specific dir with 5.32 from the compiled @INC makes it difficult to maintain custom system wide modules apart from the standard rpm/CPAN locations when upgrading.
As this is done during build, is it possible to get it added back in the next version?
Version-Release number of selected component (if applicable):
5.32
How reproducible:
perl -e 'print "@INC\n"'
Steps to Reproduce:
1. Using CVS/SCM software to update a custom module, it goes to the expected old location no longer part of @INC and the changes are not seen.
Actual results:
See above
Expected results:
The path would remain and the changes seen
Additional info:
Yes, CVS/SCM can be changed but in this case the update came across on "Thu 25 Feb 2021 04:46:53 PM CST" during updates. The installer did relocate the existing custom modules to ./5.32 but the change was not noticed until an update to one of the custom modules took place