| En brukers håndbok for Evolution | ||
|---|---|---|
| Prev | Appendix A. Frequently Asked Questions About Ximian Evolution | Next |
There are two ways to install the latest Evolution release:
If you have Ximian GNOME installed, you can start Red Carpet, Ximian's software updating system, and subscribe to the Evolution channel. This will let you install a binary for the latest release, and will also warn you when a new version has been made available.
If you want to compile from source, you can download the latest official Evolution tarball from:
Yes, if you have Ximian GNOME installed. Just run Red Carpet and subscribe to the Evolution Snapshot channel.
You can check the status of snapshots at http://primates.ximian.com/~snapshot.
Sometimes the build might fail because of problems with the source on CVS. In this case, just wait for next day's snapshot.
If you already have GNOME CVS access, simply check out the following modules: evolution, gtkhtml, gal.
If you don't have a CVS account, you can use anoncvs instead. Bear in mind that anoncvs is only synchronized once a day, and code received from anoncvs may not be latest version available.
Before using the anoncvs server, you have to log into it. This only needs to be done once. Use this command:
cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome login
|
Then you can retrieve the modules needed to compile Evolution using the following command:
cvs -z3 -d :pserver:anonymous@anoncvs.gnome.org:/cvs/gnome co evolution gtkhtml gal
|
The best way is to install Evolution into a separate prefix. In order to specify a non-default installation prefix, you can pass the --prefix option to configure or autogen.sh. For example:
cd /cvs/evolution
./autogen.sh --prefix=/opt/gnome
|
If you install Evolution and the Evolution libraries in a non-standard prefix, make sure you set the appropriate environment variables in the startup script for Evolution:
export PATH=/opt/gnome:$PATH
export GNOME_PATH=/opt/gnome:/usr
|
You may also need to add $prefix/lib (e.g. /opt/gnome/lib) to your /etc/ld.so.conf. Of course, this will not work for systems which do not use ld.so.conf, such as HP-UX.