On 26 Apr 2010, at 9:30pm, Forrie wrote: > We are using Redhat, which tends to lag behind in some versioning -- > we want to use the latest version of Subversion 1.6.x, which in turn > requires a newer version of Sqlite -- RHEL has an older version > present, which in turn is a dependency for a slew of other subsystems > (so uninstalling it would be disastrous). > > My question is essentially whether multiple versions of Sqlite can be > safely installed on the system without creating a conflict. I'm going > to "guess" that I can, especially if the newer lib is under /usr/local > and I point the ./configure process to it.
You don't really 'install' SQLite on a computer. Because it's available as source, you can compile it into any number of applications you like, install as many (shared) libraries that include it as you like, and leae as many copies of it on your hard disk as you want. So the answer to your question is that it's fine: put one copy in /usr/local, another in /libs, and another in /bin. As long as each of your programs only uses a version of SQLite it's happy with, you're fine. The trick -- if it is a trick -- is to know which one of these copies/libraries each of your apps is using. And that can be complicated with RedHat because of its (in your excellent word) slew of dependencies. If you know Redhat well enough to put the right thing in each of your configuration files, go to it. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
