3 ms·
What you say is true in theory. In the real world, the included versions of Perl and Python are for the OS and packages the OS installs. As soon as you instal
by jrockway 15y ago
What you say is true in theory. In the real world, the included versions of Perl and Python are for the OS and packages the OS installs. As soon as you install modules in the system directory or upgrade/downgrade /usr/bin/(perl|python), you run the risk of your system breaking. Perhaps this is not ideal, but it's a fact.
Amarok can do whatever you want it to, because plugins install in your home directory. Never in the course of using Amarok do you affect the system's view of what Amarok is. This is now how people treat the system Perl install; they "sudo cpan -i ..." and end up upgrading modules that the rest of the system depends on. Most of the time, this works fine, because most authors are very careful to maintain backcompat. But sometimes, it doesn't work that way, and now your system is broken.
Using your own Perl gives your application 100% control over its environment, and that's how you eliminate the unproductive task of fixing your servers (and workstations) all the time.