GNOME.org
 

[evolution-kolab] docs: updated INSTALL-notes for 3.4

commit 3fe0f937a0dd7bc5fa2047ced9a57f8443a3d6d6
Author: Christian Hilberg <hilberg kernelconcepts de>
Date:   Wed Jun 27 12:32:05 2012 +0200

    docs: updated INSTALL-notes for 3.4

 docs/manuals/INSTALL-notes |  150 +++++++++++++++++++++++---------------------
 1 files changed, 78 insertions(+), 72 deletions(-)
---
diff --git a/docs/manuals/INSTALL-notes b/docs/manuals/INSTALL-notes
index eb9af77..c275e30 100644
--- a/docs/manuals/INSTALL-notes
+++ b/docs/manuals/INSTALL-notes
@@ -3,18 +3,17 @@
 evolution-kolab - Build and install for testing purposes
 
 created:	2011-01-17 Christian Hilberg
+changed:        2012-06-19 Christian Hilberg
 
 --------------------------------------------------------------------
 
-This document briefly describes how to build, install, configure and 
-run the different parts of the evolution-kolab plugin to assist 
-testing, debugging and packaging efforts. Please understand the early 
-(late-beta) status of the evolution-kolab project. Some developer 
-skills are still needed to get all things up and running perfectly, 
-especially packaging for Debian 6.0 "Squeeze" as well as other 
-GNU/Linux- and UNIX-distributions.
+This document briefly describes how to build, install, configure and
+run the different parts of the evolution-kolab plugin to assist
+testing, debugging and packaging efforts. Please understand the early
+status of the evolution-kolab project. Some developer
+skills are still needed to get all things up and running perfectly.
 
-Hence, use evolution-kolab in production environments with special 
+Hence, use evolution-kolab in production environments with special
 care and additional safety measures.
 
 For general instructions on the "configure ; make ; make install"
@@ -34,53 +33,52 @@ Build
 
    The following tools and their dependencies need to be installed
    in order to build evolution-kolab:
-   
+
    Tool			min. Version		Ubuntu/Debian package name
-   
-   autoconf		2.65			autoconf
-   autogen		5.10			autogen
+
+   autoconf		2.68			autoconf
+   autogen		5.12			autogen
    automake		1.11			automake / automake1.11
-   autotools dev files	20090611		autotools-dev
+   autotools dev files	20110511.1		autotools-dev
    gawk			3.1			gawk
-   gcc			4.4			gcc-4.4
-   gperf		3.0			gperf
+   gcc			4.6			gcc-4.6
    gtk-doc		1.14			gtk-doc-tools
    intltool		0.41			intltool
-   libtool		2.2			libtool
+   libtool		2.4			libtool
    make			3.81			make
-   
-   
+
+
    The following libraries and their dependencies need to be installed
    in order to build evolution-kolab:
-   
+
    Library		min. Version		Ubuntu/Debian package name
-   
-   Camel		=2.30.3			libcamel1.2-dev
+
+   Camel		3.4			libcamel1.2-dev
    Curl			7.19			libcurl4-nss-dev
-   Evolution		=2.30.3			libebook1.2-dev,
+   Evolution		3.4			libebook1.2-dev,
   						libecal1.2-dev,
   						evolution-dev
-   EDS			=2.30.3			libedata-book1.2-dev,
+   EDS			3.4			libedata-book1.2-dev,
    						libedata-cal1.2-dev,
    						libedataserver1.2-dev,
    						libedataserverui1.2-dev,
    						libebackend1.2-dev,
    						evolution-data-server-dev
-   Glib			2.0			libglib2.0-dev
-   GMime		2.4			libgmime-2.4-dev
-   GTK+			2.0			libgtk2.0-dev
+   Glib			2.30			libglib2.0-dev
+   GMime		2.4 or 2.6		libgmime-2.4-dev, libgmime-2.6-dev
+   GTK+			3.2			libgtk-3-dev
    ICAL			0.44			libical-dev
    NSS3			3.12			libnss3-dev
-   Soup			2.30			libsoup2.4-dev,
+   Soup			2.36			libsoup2.4-dev,
    						libsoup-gnome2.4-dev
-   SQLite3		3.6			libsqlite3-dev
+   SQLite3		3.7			libsqlite3-dev
 
 1. Create a build directory
 
 2. "cd" to the build directory and run
 
     </absolute/path/to/evolution-kolab-source>/autogen.sh
-   
+
    (autogen.sh needs to be run with absolute path here,
    otherwise gtk-doc will fail to build the API documentation)
 
@@ -88,23 +86,20 @@ Build
 
     </absolute/path/to/evolution-kolab-source>/configure <configure-opts>
 
-   <configure-opts> must contain "--enable-largefile", if
+   <configure-opts> should contain "--enable-largefile", if
    Evolution-Data-Server was built with largefile support.
 
    If autogen.sh calls configure for you, supply the
    <configure-opts> to autogen.sh instead of configure.
-   
+
    evolution-kolab is built and tested by its maintainers with the
    following flags (to be passed to autogen.sh or configure):
-   
-     Ubuntu 10.04 "Lucid Lynx":
-     --enable-gtk-doc --enable-largefile --enable-maintainer-mode 'CFLAGS=-g -O0 -fPIC'
-     
-     Debian 6.0 "Squeeze":
-     --enable-gtk-doc --disable-largefile --enable-maintainer-mode 'CFLAGS=-g -O0 -fPIC'
+
+     Ubuntu 11.10 "Oneiric Ocelot" and above:
+     --prefix=/usr/local --enable-gtk-doc --enable-largefile=no --enable-maintainer-mode 'CFLAGS=-g -O0 -fPIC'
 
 4. In the build directory, run
-    
+
     make
 
 
@@ -118,14 +113,19 @@ In the build directory, run "make install" (super user privileges may be needed)
 
 It is recommended for time being that evolution-kolab be installed to
 /usr/local (the default prefix, change it via configure if needed)
-to avoid messing up the /usr directory.
+to avoid messing up the /usr directory. A few libraries will be installed
+under /usr nonetheless, but having the majority of the libraries installed
+under /usr/local minimizes the impact on the default installation
+locations.
 
 Presently, not every component of evolution-kolab is installed into
 the right place (and some cruft gets installed still which need not be),
 so it is best to select an installation directory other than /usr which
-can easily be cleaned up.
+can more easily be cleaned up.
 
-We'll assume evolution-kolab got installed under /usr/local (default).
+We'll assume most of evolution-kolab got installed under /usr/local
+(default). However, some installation paths are retrieved from pkg-config,
+so they will differ from /usr/local (/usr/lib, most likely).
 
 
 --------------------------------------------------------------------
@@ -134,20 +134,15 @@ Install the Kolab IMAP provider
 
 --------------------------------------------------------------------
 
-The following symlinks need to be created:
-
- cd /usr/lib/evolution-data-server-1.2/camel-providers
- ln -s /usr/local/lib/evolution-data-server-1.2/camel-providers/libcamelkolab.so .
- ln -s /usr/local/lib/evolution-data-server-1.2/camel-providers/libcamelkolab.urls .
-
-'kolab2' is now available as protocol type for email access.
+The Camel provider installation directory is retrieved from pkg-config.
+The following files will be installed:
 
+libcamelkolab.la
+libcamelkolab.so
+libcamelkolab.urls
 
-Note for Debian 6.0 "Squeeze":
-
-The installation path for the Camel providers is
-/usr/lib/evolution-data-server-1.2/camel-providers-14
-so be sure to use that path in the above command lines instead.
+The installation path typically is
+/usr/lib/evolution-data-server/camel-providers
 
 
 --------------------------------------------------------------------
@@ -156,22 +151,30 @@ Install the Kolab calendar and addressbook backends
 
 --------------------------------------------------------------------
 
-The following symlinks need to be created:
+Analogous to the Camel provider libraries, the installation paths
+for the Evolutoin Data Server addressbook backend and calendar backend
+are retrieved from pkg-config. The path names below are the most
+likely, but depend on your pre-packaged Evolution and Evolution Data
+Server.
+
+The following files will be installed:
 
- cd /usr/lib/evolution-data-server-1.2/extensions
- ln -s /usr/local/lib/libecalbackendkolab.so .
- ln -s /usr/local/lib/libebookbackendkolab.so .
+libebookbackendkolab.la, libebookbackendkolab.so in
+/usr/lib/evolution-data-server/addressbook-backends
 
- cd /usr/lib/evolution/2.30/plugins
- ln -s /usr/local/share/evolution-kolab/org-gnome-kolab.eplug .
- ln -s /usr/local/lib/liborg-gnome-kolab.so .
+and
 
-If the environment varaiable LD_LIBRARY_PATH does not contain the 
+libecalbackendkolab.la, libecalbackendkolab.so in
+/usr/lib/evolution-data-server/calendar-backends
+
+If the environment varaiable LD_LIBRARY_PATH does not contain the
 path /usr/local/lib (check with "echo $LD_LIBRARY_PATH"), it needs to be added,
 e.g. by issuing
 
  export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/local/lib"
 
+This is important since the rest of the evolution-kolab libraries
+are being installed under /usr/local.
 
 --------------------------------------------------------------------
 
@@ -210,41 +213,44 @@ Use the Kolab calendar and addressbook backends
 --------------------------------------------------------------------
 
 The Kolab calendar/addressbook backend, as well as memos and tasks, can
-be used without further configuration (presently). Some issues need to
+be used without further system level configuration (presently). Some issues need to
 be taken care of, however:
 
 - after (better: before) installation, make sure to exit Evolution. Make sure that
   all Evolution Data Server *factory* processes have terminated. If you are using the GNOME
   desktop, GNOME may keep the factory processes alive. Kill them, e.g. by
   issuing both of the following commands:
-  
-   killall e-calendar-factory
-   killall e-addressbook-factory
+
+   killall evolution-calendar-factory
+   killall evolution-addressbook-factory
 
 - Evolution can now be started again. If a backend does not come up properly
   (no Kolab calendar type available, same goes for addressbook, memos or
   tasks), make sure the Evolution Data Server finds all of its
   libraries. The calendar backend factory process is started by hand as follows:
 
-   /usr/lib/evolution/e-calendar-factory
+   /usr/lib/evolution/evolution-calendar-factory -r
 
   (Make sure /usr/local/lib is in LD_LIBRARY_PATH, see above.)
   If doing so, make sure all factory processes have terminated before starting them
   by-hand, and also start Evolution only after the backend factories have come up.
-  
+
   Starting the address book factory process is done via the command
-  
-   /usr/lib/evolution/e-addressbook-factory
 
+   /usr/lib/evolution/evolution-addressbook-factory -r
+
+  Both processes must show "kolab" as one of the supported protocols
+  in their console startup messages, orelse connection to a Kolab
+  server will not work.
 
-An existing addressbook from the Kolab server can now be added to the 
+An existing addressbook from the Kolab server can now be added to the
 list of addressbooks in Evolution's "Contacts" view. An existing calendar
-from the Kolab server can now be added to the list of calendars 
+from the Kolab server can now be added to the list of calendars
 Evolution's "Calendar" view. Likewise applies to tasks and memos.
 
 Setting up one of the above types (calendar, contacts, memos or tasks) in
 the corresponding view:
-1. Select File->New->Addressbook/Calendar/Task List/Memo List, 
+1. Select File->New->Addressbook/Calendar/Task List/Memo List,
    - enter a display name, i.e. the name that will be shown in the selector area
    - choose from the checkboxes the desired options
    - enter the Kolab server hostname (FQDN) or IP address
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]