On Wed, Aug 8, 2012 at 11:51 AM, Tilsley, Jerry M.
<jmtils...@st-claire.org> wrote:
>
> Sorry, I'm going by a Centos install which is usually the same but
> maybe there is some difference. On Centos, sqlite 3.6.20 is the
> current stock version and what other packages should expect. I'd
> look at the problem the other way and figure out why your other user has
> something out of date in his library path.
>
> The user has an out of date package because the user and package are part of
> a large data interfacing system for a hospital. I would like for that user
> to be able to check scripts in, but because of the vendor system relies on
> the older version of sqlite, the user has to use that version.
Linux itself is relatively flexible about library paths and multiple
versions of things, but the RPM packaging system generally just wants
to manage a single version at a time on a machine (with a few
exceptions). Some brute-force solutions would be to recompile from
source, either with a static linkage to the current library or on the
target machine against the outdated libs. Or copy the current .so
file over to some other path that you would add to LD_LIBRARY_PATH in
the environment when running svn. Or if you don't care about branch
tracking, you might compile a 1.5 version from source that would not
have the library requirement but still has wire-protocol
compatibility.
--
Les Mikesell
lesmikes...@gmail.com
