You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this will probably corrupt the packages handled by the system (usually on Linux systems). Instead, suggest to the user to use a local::lib-based environment.
force install is a bad practice. If DBI doesn't install, there is a good reason that must be fixed, either on the system or in DBI.
The text was updated successfully, but these errors were encountered:
Thank you for the feedback. I will fix the README to advise an upgrade via the OS-specific mechanism. If no recent DBI package is available this way, then uninstall the one provided by the OS and perform a non-forced install via CPAN. Would you agree that such advice would be safe to give?
If the sysadmin installs DBI from the CPAN and then installs DBI from the package manager, the one from the package manager will override the one from the CPAN. So that is not a better solution.
So, no, this is not a good advice either.
The proper way is to avoid installing Perl modules in a place that is handled by the OS and to set PERL5LIB to point to that area. local::lib is an helper module for that task.
Another solution is to avoid to use /usr/bin/perl to run applications and instead to build your own perl and to deploy it with your application.
The installation instructions says:
sudo perl -MCPAN -e 'force install DBI'
This is very bad practice because:
local::lib
-based environment.force install
is a bad practice. If DBI doesn't install, there is a good reason that must be fixed, either on the system or in DBI.The text was updated successfully, but these errors were encountered: