Re: I nuked script.pm. Now postgres don't want to talk to me

[davido]

Was this system Perl? Is it Debian? If so: (Stack Exchange) Unix & Linux: How can I completely reinstall Perl on Debian without having functional Perl?

It sounds like that's pretty much where you are at.

In the future you may consider leaving system-Perl alone and using perlbrew or plenv. Either one of those would allow you to use a totally different install of Perl (and Perl libraries) for your own projects, and leave the system Perl alone for the system. It does turn out to be a safer "best practice".

Better yet, set up containers in the future.

[pvaldes]

Some notes:

In order to have the perl commmand working again I had to restore Strict.pm and Tabs.pm (called by diagnostics), chmod o+r them, and restore exec for other (chmod o+x) in several parent directories.

in order to restore psql I had to reinstall again libsocket-perl to upgrade socket object version, restore Glob.pm, and chmod o+r them

By now is working and I'm learning, so is a happy end. Revenge against CPAN pending. There is nothing like putting yourself in troubles and out of your commandfort zone sometimes