|There's more than one way to do things|
Updating Config.pmby morgon (Deacon)
|on Feb 23, 2013 at 19:27 UTC||Need Help??|
morgon has asked for the
wisdom of the Perl Monks concerning the following question:
recently I had some troubles Installing Glib on Debian and after some digging the root-cause of my problems seemed to be a Config.pm that did not properly reflect the system anymore.
It turned out that the "libpth"-entry in Config.pm contained "/usr/lib64" (a directory that does not exist on the system), but not "/usr/lib/x86_64-linux-gnu" (this entry controls which directories ExtUtils::Liblist searches).
I have no idea how Config.pm and the system-state diverged (I assume the system was updated but not the perl) but I have anually updated Config.pm and everything works fine so far.
My questions would be: Is manually updating Config.pm an acceptable risk or do I run the dager of some problems further down the road?
And are the any tools for bringing back Config.pm to properly reflect a changed system?