User Guide

* Install Guide
* Users Manual
* BugFixes
* Serious Involvement
* More Info

Please feel free to skip any section of this which seems blatantly obvious, for most of you that will be most of this page.

Install Guide

eJourn can be installed using the standard configure, make procedure. But here's a guide to your options and some advanced installation stuff. Also, I'll cover the basics:

Autopackage

The Autopackage installer is available for ease of use. Simply follow these steps:

wget http://www.public.iastate.edu/~chris129/code/ejourn/eJourn-0.1.5.x86.package
chmod +x eJourn-0.1.5.x86.package
./eJourn-0.1.5.x86.package
You may put in your root password, but it's not necessary for eJourn. Autopackage will need your root password if you don't already have it. Autopackage will be installed by the eJourn package, so don't worry about installing it; it's done for you.

The autopackage requires you to be using linux. Not BSD, not OS X. Linux.

Source

The source building is fairly easy. First I'll cover the root method, then the user method.

./configure --prefix=/usr/local/
make install

Without Root privs:

echo "export LD_LIBRARY_PATH=\"$LD_LIBRARY_PATH:/home/yourusername/lib\"" >> ~/.bashrc
echo "export PATH=\"$PATH:/home/yourusername/bin\"" >> ~/.bashrc
./configure --prefix=/home/yourusername/
make install

This is adding the library directory to your path and installing to your home directory. It's semi-standard to install into a home directory without root privs. Of course, you will be the only user on your system to benefit from the install.

RPM

This is only for Fedora 4 users.

rpm -ihv eJourn-0.1.5.rpm

User Manual

The Users Manual is now available online in English. It's also available with the program.

BugFixes

This section will host interesting new bugfixes that may have been driving you batty.

Serious

If you'd like to become seriously involved in eJourn use/development please e-mail me. I can use talented artists, translators, developers, and even just bug reports. Remember, a good bug report includes: Exact reproduction steps, description of the fault, and occurance odds (does it always do it, or sometimes?). eJourn also badly needs documentation. This can be user documentation, and it can be developer documentation; anyone should be able to write user documentation.
A great way to get involved is to join our Mailing List. Anyone is welcome to join and post!