On the 3rd hand (Medusa here) those of us involved in mission critical apps refuse to let people arbitrarily update packages that are part of the "system". Things like the bug introduced in 3.7.12 being a prime example.
It's called "Configuration Control". Some apps may depend on updated system libraries...just keep them out of my sandbox. If our app needs a fix WE put it in under a controlled manner with regression testing, test system, and final deployment. And we may include a newer version than the system is allowed to have. Call me (and my configuration control panel) control freaks. We used to have tons of problems on Solaris due to shared libraries. Numerous incompatibilities across multiple versions of Solaris. Static link always worked. Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Pavel Ivanov [paiva...@gmail.com] Sent: Friday, May 25, 2012 7:27 AM To: General Discussion of SQLite Database Subject: EXT :Re: [sqlite] What does "The use of the amalgamation is recommended for all applications." mean, precisely? OTOH, all people involved in supporting Linux distributions advocate against static inclusion and for use of dynamic libraries all the time so that if some bug or security vulnerability is fixed in SQLite it could be easily updated for everybody by upgrading only one package. I don't know though what they suggest to do if you need to use version of SQLite newer than distribution is currently providing. Pavel _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
