You are not logged in.
Like many developers who use perl I need extra modules that do not come from the standard Arch repo. So I have them installed from CPAN with cpan. Today I noticed that half of my application broke, complaining that it can't locate modules I know for a fact I installed. Those missing modules happen to be from CPAN.
I checked and found them in /usr/lib/perl5/5.34/site_perl/. My current perl version however is 5.36. pacman righteously produces an "error: No package owns /usr/lib/perl5/5.34" and correctly mentions cpan as a possible culprit. At the same time cpan no longer sees /usr/lib/perl5/5.34/site_perl/ directory and doesn't re-create the modules previously installed into the current site_perl directory.
So I end up with a system that has broken/missing modules on the one hand and leftover/garbage on the other.
My question is not about how to fix it. I am rather interested in having a proper or elegant way to manage perl version upgrades without repeated manual cleanup and module re-install. Maybe such a mechanism already exists, e.g. if I were to type "cpan version-upgrade" which would rebuild modules previously installed for the older version into the new perl version directory and then clean up the old directories that would be great. This post explains it but offers no civilized or automated solution.
Help? ¯\_(ツ)_/¯
Last edited by cherio (2022-06-03 21:23:51)
Offline