Bibledit needs some libraries and tools which are not installed on most standard installations of Linux. Therefore you need to install these before installing Bibledit. In most cases it is sufficient to install the development packages of Gtk2 and sqlite3 and all their dependencies.
To help you with it, some example prepared installations are given below.
When through, open a terminal. This is going to be used in the next few steps.
If you know that your Linux distribution comes with sqlite3, you can skip this step. For example, Fedora Core 5 comes with it, and Ubuntu 5.10, and Debian Etho.
Download a version of sqlite3, e.g. sqlite-3.3.4.tar.gz, from http://www.sqlite.org.
Move it to the home directory.
To verify the package is there, type
ls
To unpack sqlite3 type
tar zxf sqlite-3.3.4.tar.gz
To enter the newly created directory, type
cd sqlite-3.3.4
To configure sqlite, type
./configure --prefix=/usr
Watch many messages, but no errors.
To compile sqlite, type
make
Watch many messages, but no errors.
To install sqlite, type
sudo make install
and provide the password.
Watch many messages, but no errors.
To go back to the home directory, type
cd
Optionally the tarball and the directory it made can be cleaned away. To do that, type
rm -rf sqlite-3*
If you know that your Linux distribution comes with bibledit, you can skip this step. For example, Debian Etho comes with it.
Note. In case of upgrading, Bibledit ought to be installed while it is not running.
Download package bibledit-x.x.tar.gz (x.x is to be replaced with the actual version number).
Move it to the home directory.
In the terminal, to verify the package is there, type
ls
To unpack bibledit type
tar zxf bibledit-x.x.tar.gz
To enter the newly created directory, type
cd bibledit-x.x
To configure bibledit, type
./configure
Watch many messages, but no errors.
To compile bibledit, type
make
Watch many messages, but no errors.
To install it, type
sudo make install
and give the password. Or if this does not work, type su, and provide the password, then type make install, then type exit to become a normal user again.
Watch many messages, but no errors.
To go back to the home directory, type
cd
Optionally the tarball and the directory it made can be cleaned away. To do that, type
rm -rf bibledit-*
Optionally you can add a launcher to the panel.
To start bibledit, type
bibledit &
Download a Sun Java virtual machine from http://www.java.com/en/download/linux_manual.jsp.
Choose the "Linux (self extracting file)", which gives a file called jre-1_5_0_06-linux-i586.bin in the home directory, or a higher version.
In the terminal, to verify the package is there, type
ls
To install the package, type
sh jre-1_5_0_06-linux-i586.bin
Agree to the license and complete installing Java.
Make a note of the directory where Java got installed. In this case this is ~/jre1.5.0_06
Note. If you install it in the directory given above, then Bibledit will find Java automatically. If you install it elsewhere, you need to enter the path to Java by hand.
Note. Some Linux distributions come with their own version of Java installed. It may be quite a hassle to find out where this version of Java has been installed, and so it may be difficult to locate it in Bibledit. In case you encounter trouble to find that directory, it will be easier to just download the Java version as described above, and install it following the instructions. And moreover, the GNU version of Java, gij, is not enough for XEP. Hence, if this version comes with your Linux distribution, you still need to install the one from Sun.