Is sqlite 3.8.3 "good enough"

Help & Support
1

I am deploying to a Amahi Home Server running on Fedora 19

Amahi Home Server installs sqlite 3.8.3

I have started drone from the command line and opened the page in a browser. If that is “good enough” I’d like to keep my setup there.

2

As mentioned on IRC, it should be good enough as long as its running, not aware of any reason to avoid 3.8.3.

3

I added instructions for compiling sqlite 3.8.5 and installing to a different directory than the system version - this would allow you to keep both versions while using 3.8.5 for nzbdrone.

It’s really simple, assuming you have the prerequisite packages (gcc-c++ / gcc / curl)

  1. Download sqlite3.8.5 source and extract it

    curl -L http://www.sqlite.org/2014/sqlite-autoconf-3080500.tar.gz -o /tmp/sqlite-autoconf-3080500.tar.gz
tar -zxvf /tmp/sqlite-autoconf-*.tar.gz -C /tmp/

  2. Compile sqlite3.8.5

    cd /tmp/sqlite-autoconf*

sudo ./configure --prefix=/opt/sqlite3.8.5          \
                 --disable-static                   \
                 CFLAGS=" -Os                       \
                 -frecord-gcc-switches              \
                 -DSQLITE_ENABLE_COLUMN_METADATA=1"

sudo make
sudo make install

The only caveat is you will need to call (run) nzbdrone with a different PATH and LD_LIBRARY_PATH like this:

export LD_LIBRARY_PATH=/opt/sqlite3.8.5/lib   && \
export PATH=/opt/sqlite3.8.5/bin:$PATH        && \
/opt/mono/bin/mono /opt/nzbdrone/NzbDrone.exe

It’s all outlined in the CentOS 6 wiki section

4

Thanks for the help.

If 3.8.3 is “good enough” and since I can start DD with sqlite 3.8.3 I’d like to keep it that way as it simplifies delivery of the server to a friend is is NOT Linux savy (and I have only limited Linux expertise).

I have updated the .bash_profile of the user profile I expect will be running all mono services to include a call to the /opt/mono/env.sh script which sets the environment variables for the mono runtime delivered by the pakorra/opensuse mono repository so that mono runtime should always be available.

The fewer “special handling” requirements, the better.