stuart: doc/www/src cvs-kolab.html.m4,1.3,1.4
cvs at intevation.de
cvs at intevation.de
Mon Apr 26 17:22:40 CEST 2004
Author: stuart
Update of /kolabrepository/doc/www/src
In directory doto:/tmp/cvs-serv27779
Modified Files:
cvs-kolab.html.m4
Log Message:
Updated Webclient install guide, corresponding the the new release (i.e. all webclient code is now in Horde).
Index: cvs-kolab.html.m4
===================================================================
RCS file: /kolabrepository/doc/www/src/cvs-kolab.html.m4,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- cvs-kolab.html.m4 19 Jan 2004 13:20:35 -0000 1.3
+++ cvs-kolab.html.m4 26 Apr 2004 15:22:37 -0000 1.4
@@ -28,39 +28,600 @@
Please report any development issues to the public mailinglist
<a href="mailto:kolab-devel at intevation.org">kolab-devel at intevation.org</a>.
-<h3>Building and Installing the Kolab WebClient development version</h3>
-<font size="-1">(Thanks to cle_kolab At gmx.net)</font><p>
+<hr />
+<h3>Kolab Webclient</h3>
+<h4>How to get it; How to configure it; How to run it.</h4>
-1) Download the tar from :
-<a href="http://intevation.de/cgi-bin/viewcvs-kolab.cgi/server/horde/?only_with_tag=KOLAB_1_0">Kolab CVS</a><br>
+<div align="right">April 2004</div>
-2) tar xfvz horde.tar.gz <br>
-3) cd horde <br>
-4) make <br>
-5) rpm -Uhv file:///kolab/RPM/PKG/horde-*.kol.rpm <p>
+<p>Please direct any comments and suggestions about this guide to
+<a href="mailto:s.binge at codefusion.co.za">Stuart Bingë</a></p>
-6) add the following directive to /kolab/etc/kolab/httpd.conf.template <br>
+<h4>What's New?</h4>
+<ul>
+<li>Multiple calendar, notepad and tasklist support (each calendar, notepad and tasklist
+is stored in a separate IMAP folder).</li>
+<li>Calendar, Note and Task sharing. Currently this is a two-step process (unfortunately),
+but simplifying this to a single-step procedure is definitely on our todo. What you
+need to do is go into IMP (the Mail client), and share the folder via Cyrus ACLs.
+You then need to go into the respective application (Kronolith, Mnemo, Nag) and share
+the calendar corresponding the the IMAP folder you shared, mirroring the ACL settings
+you specified in IMP.</li>
+<li>Full filter support for mail, through the Ingo application. This also allows
+for more powerful vacation and forwarding support than the previous vacation
+and forwarding modules.</li>
+<li>No more 'meetings' application for viewing free/busy information and inviting
+attendees. All this functionality has been ported (by yours truly) to Kronolith,
+meaning all events you create in your calendar can support attendees.</li>
+<li>Many minor fixes and improvements including an improved UI, as the Horde
+project has evolved substantially as we have been developing the Webclient
+functionality. This also means that the 'Layout' option on the Horde portal
+now works - you are able to customise your front page to display mail/note/task/etc
+summaries, as well as additional blocks such as Google search, in any configuration
+that you like. There's even a Kolab theme that you can use :-)</li>
+</ul>
+
+<p><b>PLEASE NOTE:</b> The Webclient, while technically feature-complete, is still
+considered development quality. As such it is not recommended that you run
+it in a production environment, however any and all potential testers are most welcome.
+There are most probably a whole host of bugs left in the code, and a lot of improvements
+can still be made, however as it stands it is a very usable product.</p>
+
+<p>Also note
+that while this is considered the 'Kolab Webclient', it is still based on an
+existing project (the <a href="http://www.horde.org/">Horde</a> project), and
+as the current Webclient codebase is contained in Horde's CVS repository it relies
+an an underlying code base that is also under constant development. What this
+boils down to is any bugs that you may encounter might not necessarily be related
+the the Kolab Webclient portion of the code, but instead be within the Horde code
+itself.</p>
+
+<p>Currently the Webclient does not interoperate with the Kolab KDE Client, nor
+any Outlook-configured mailboxes, so any users that are to use the Webclient should
+do so exclusively. Interoperability is most definitely one of the upcoming features
+you can look forward to - even between Outlook mailboxes and the Webclient.</p>
+
+<p>Any commentary about the Webclient should be directed either to the
+<a href="http://lists.horde.org/mailman/listinfo/dev">Horde development list</a>
+or to the <a href="http://www.kolab.org/mailman/listinfo/kolab-devel">Kolab development list
+</a>. We should pick up discussion on either.</p>
+
+<p>This guide assumes you will be running Horde & Kolab on the same machine.
+It should technically be possible to separate the two; however, as of yet this
+has not been attempted. If you manage to do this we would greatly appreciate
+feedback as to how you did it, and we'll include it in this guide.</p>
+
+<p>This guide also assumes that your kolab installation is in <code>/kolab</code>
+- if it's not then just substitute in your specific kolab root location wherever
+you see the directory <code>/kolab</code> in this document.</p>
+
+<p>The following conventions are used, and assumptions made, in this document:
+<ul>
+<li>Commands that should be entered at the shell are preceded by hashes (<code>#</code>).</li>
+<li>You will be installing the Webclient as the root user.</li>
+
+<li>You installed Kolab through the <a href="http://www.zfos.org/">ZfOS</a> OBMTOOL
+method.</li>
+
+<li>You are working in the Kolab environment while installing the Webclient
+(e.g. by running <code><a href="#opa">opa</a> /kolab</code>).</li>
+
+<li>You should create a temporary directory for use in the initial setup
+steps, while the necessary packages are being downloaded - the files should
+only be moved to their final locations once everything is in place. Once
+everything is installed you can remove this temporary directory; in this
+guide <code>/tmp</code> is used as the temporary location.</li>
+
+<li>It is recommended that you put the following in your root users' <code>~/.cvsrc</code>:
<pre>
-<Directory "/kolab/var/kolab/www/horde>
- Options +FollowSymLinks
- AllowOverride None
+cvs -z3
+update -d -P
+checkout -P
+diff -u
+</pre>
+</li>
+</ul>
+</p>
- php_value include_path '/kolab/lib/php/pear/:.'
- php_flag magic_quotes_gpc Off
- php_flag track_vars On
- Order allow,deny
- Allow from all
-</Directory>
+<h4>Pre-installation</h4>
+<p>First of all you need to ensure your Kolab distribution is able to run Horde.
+This means installing additional OpenPKG RPMs and recompiling your Apache RPM
+with additional flags. You can obtain source RPMs from the <a
+href="ftp://ftp.openpkg.org/release/2.0/SRC/">OpenPKG 2.0 Source Repository</a>, or
+if you'd prefer and are running Kolab on an OpenPKG-supported platform, you
+can obtain binary RPMs from the <a href="ftp://ftp.openpkg.org/release/2.0/BIN">
+OpenPKG 2.0 Binary Repository</a></p>
+<p>The necessary packages are:</p>
+
+<pre>
+libxml-2.6.6-2.0.0
+libxslt-1.1.3-2.0.0
+mysql-4.0.18-2.0.0
</pre>
-7) and then run /kolab/etc/kolab/kolab -v -o <br>
+<p>Apache needs to be re-compiled with the following additional flags:</p>
-8) Restart apache/kolab <br>
+<pre>
+--with=mod_php_dom
+--with=mod_php_mysql
+</pre>
-To access your web frontend goto: http://mykolabserver/horde <br>
+<p>For your convenience I've included an updated Kolab/OpenPKG 2.0 obmtool.conf in
+<a href="#obmconf">Appendix B</a> that can be used to set up a Horde-capable Kolab
+installation.
+</p>
-<p>
+<p>Be sure to change your MySQL root password to something secure after installing
+MySQL. You can do this by running the following command:<p>
+
+<pre>
+# mysqladmin -u root password "your-mysql-root-pw"
+</pre>
+
+<h4>Optional Step</h4>
+<p>Install a PHP Accelerator.</p>
+
+<p>This step is not critical to get Horde running, however it is highly recommended
+if you want to have as responsive a Webclient as possible. This guide instructs on
+how to install the <a href="http://www.phpaccelerator.co.uk/">ionCube PHP Accelerator</a>,
+as it is exceptionally simple to set up and provides a very noticeable performance boost.
+If you prefer other accelerators and are able to get them to work with Kolab then please
+send instructions on how to install them and we'll put it up here.</p>
+
+<p>Download the relevant package for your platform and PHP version from the
+<a href="http://www.phpaccelerator.co.uk/download.php">ionCube Downloads Page</a>. As of
+time of writing for x86 Linux, this would be
+<a href="http://www.phpaccelerator.co.uk/releases/linux_i686-glibc2.1.3/1.3.3r2_4.3.0/php_accelerator-1.3.3r2_php-4.3.0_linux_i686-glibc2.1.3.tgz">1.3.3r2</a>
+for PHP version 4.3.0. You should read the INSTALL and CONFIGURATION files that are
+distributed with PHPA for details on how to fine-tune performance. If you just want to
+quickly set up an accelerated environment for use with Horde then the following commands
+should be suitable:</p>
+
+<pre>
+# cd /tmp
+# tar xvjf php_accelerator*.tgz
+# mv php_accelerator*/php_accelerator*.so /kolab/lib
+# chown kolab:kolab /kolab/lib/php_accelerator*.so
+</pre>
+
+<p>The following then needs to be added to <code>/kolab/etc/kolab/php.ini.template</code>:
+
+<pre>
+; PHP Accelerator extension
+zend_extension="/kolab/lib/php_accelerator_1.3.3r2.so"
+
+; This should be as large as you can spare. The default is 8, which is not
+; optimal for a project as large as Horde.
+phpa.shm_size = 16
+</pre>
+
+<p>It is also recommended that you increase the value of <code>memory_limit</code> in
+<code>/kolab/etc/kolab/php.ini.template</code> to 12M or even 16M, for optimal use with
+Horde.</p>
+
+<p>After saving <code>/kolab/etc/kolab/php.ini.template</code> run <code>kolabconf</code>
+to re-generate <code>php.ini</code> and restart the Apache server. You can test to see if
+the extension is operational by viewing the following script through your Kolab web server.</p>
+
+<pre>
+<?php phpinfo(); ?>
+</pre>
+
+<p>You should see something similar to the following after the initial version information:</p>
+
+<pre>
+This program makes use of the Zend Scripting Language Engine:
+Zend Engine v1.3.0, Copyright (c) 1998-2003 Zend Technologies
+with the ionCube PHP Accelerator v1.3.3r2, Copyright (c) 2001-2002,
+by Nick Lindridge
+</pre>
+
+<p>PHP Accelerator is now installed. Any PHP script viewed through your Kolab webserver will
+have its bytecode cached by PHPA - note that if you are experiencing 'weirdness' when it
+comes to viewing in-development scripts (for example, your changes are not coming through
+or incorrect errors are being generated) then your PHPA cache may need to be refreshed.
+The easiest way to do this is to just stop Apache and <code>rm /tmp/phpa*</code>.</p>
+
+<p>Now then, on to the actual Webclient installation instructions.</p>
+
+<h4>Step 1</h4>
+<p>Download and install the necessary PEAR packages.</p>
+
+<p>1. Horde's PEAR distribution:</p>
+<pre>
+# cd /tmp
+# wget ftp://ftp.horde.org/pub/pear/pear-1.3.tar.bz2
+# tar xvjf pear-1.3.tar.bz2
+# cd pear
+# rm pearcmd.php
+# cp -R * /kolab/lib/php/
+</pre>
+
+<p>2. Miscellaneous PEAR packages from PEAR CVS (Instructions from
+<a href="http://www.php.net/anoncvs.php">http://www.php.net/anoncvs.php</a>)</p>
+
+<pre>
+# cd /tmp
+# cvs -d :pserver:cvsread at cvs.php.net:/repository login
+</pre>
+<p>(When asked for a password, use 'phpfi').</p>
+<pre>
+# cvs -d :pserver:cvsread at cvs.php.net:/repository checkout pear/HTTP_WebDAV_Client
+# pear install pear/HTTP_WebDAV_Client/package.xml
+</pre>
+
+<h4>Step 2</h4>
+<p>Check out the necessary Horde modules from Horde's CVS (instructions from
+<a href="http://www.horde.org/source/using.php">http://www.horde.org/source/using.php</a>):</p>
+
+<pre>
+# cd /tmp
+# cvs -d :pserver:cvsread at anoncvs.horde.org:/repository login
+</pre>
+<p>(When asked for a password, use 'horde').</p>
+<pre>
+# cvs -d :pserver:cvsread at anoncvs.horde.org:/repository checkout horde framework imp kronolith mnemo nag passwd turba ingo
+# find . -type d -name CVS | xargs rm -rf
+</pre>
+
+<h4>Step 3</h4>
+<p>Install the Horde framework:</p>
+
+<pre>
+# cd /tmp/framework
+# php install-packages.php
+</pre>
+
+<h4>Step 4</h4>
+<p>Move the default Horde configuration files to their final locations:</p>
+
+<pre>
+# cd /tmp
+# mv horde/config/conf.php.dist horde/config/conf.php
+# mv horde/config/prefs.php.dist horde/config/prefs.php
+# mv horde/config/mime_drivers.php.dist horde/config/mime_drivers.php
+# mv horde/config/html.php.dist horde/config/html.php
+# mv horde/config/nls.php.dist horde/config/nls.php
+# mv horde/config/hooks.php.dist horde/config/hooks.php
+# mv horde/config/registry.php.dist horde/config/registry.php
+# mv imp/config/html.php.dist imp/config/html.php
+# mv imp/config/mime_drivers.php.dist imp/config/mime_drivers.php
+# mv imp/config/prefs.php.dist imp/config/prefs.php
+# mv imp/config/servers.php.dist imp/config/servers.php
+# mv ingo/config/prefs.php.dist ingo/config/prefs.php
+# mv ingo/config/backends.php.dist ingo/config/backends.php
+# mv ingo/config/fields.php.dist ingo/config/fields.php
+# mv kronolith/config/html.php.dist kronolith/config/html.php
+# mv kronolith/config/prefs.php.dist kronolith/config/prefs.php
+# mv mnemo/config/prefs.php.dist mnemo/config/prefs.php
+# mv nag/config/html.php.dist nag/config/html.php
+# mv nag/config/prefs.php.dist nag/config/prefs.php
+# mv passwd/config/backends.php.dist passwd/config/backends.php
+# mv turba/config/html.php.dist turba/config/html.php
+# mv turba/config/prefs.php.dist turba/config/prefs.php
+# mv turba/config/attributes.php.dist turba/config/attributes.php
+# mv turba/config/sources.php.dist turba/config/sources.php
+</pre>
+
+<h4>Step 5</h4>
+
+<p>Some Horde configuration files need to be edited by hand; the rest
+can be auto-generated through the Horde Admin interface. You may want
+to <code>chmod 0600</code> these files for additional security. The files
+you need to edit, and what needs to be done in each file, is as follows:</p>
+
+<dl>
+<di><code>horde/config/registry.php</code></di>
+<dd>Delete all the <code>$this->applications['XXX']</code> blocks except the following:
+<code>$this->applications['horde']</code>, <code>$this->applications['logout']</code>,
+<code>$this->applications['problem']</code>, <code>$this->applications['imp']</code>,
+<code>$this->applications['ingo']</code>, <code>$this->applications['turba']</code>,
+<code>$this->applications['kronolith']</code>, <code>$this->applications['mnemo']</code>,
+<code>$this->applications['nag']</code> and <code>$this->applications['passwd']</code>.
+For each of these remaining blocks, delete the line that says <code>'menu_parent' => 'XXX'</code>.
+</dd>
+
+<di><code>imp/config/servers.php</code></di>
+<dd>Delete all the <code>$servers['XXX']</code> blocks except the
+<code>$servers['kolab']</code> definition (should be right at the end
+of the file).</dd>
+
+<di><code>ingo/config/backends.php</code></di>
+<dd>Delete all the <code>$backends['XXX']</code> blocks except the
+<code>$backends['kolab']</code> definition (should be right at the end
+of the file).</dd>
+
+<di><code>passwd/config/backends.php</code></di>
+<dd>Delete all the <code>$backends['XXX']</code> blocks except the
+<code>$backends['kolab']</code> definition (should be right at the end
+of the file).</dd>
+
+<di><code>turba/config/sources.php</code></di>
+<dd>Delete all the <code>$cfgSources['XXX']</code> blocks except the
+<code>$backends['kolab_global']</code> and <code>$backends['kolab_local']</code>
+definitions (should both be the last two entries in the file).</dd>
+</dl>
+
+<h4>Step 6</h4>
+<p>Move the horde directories to their final location. Note that you can put
+the Webclient in whatever directory you want and link to it from your
+Kolab WWW directory, however in this document we just move the Horde
+directories directly into the WWW directory.</p>
+
+<pre>
+# cd /tmp
+# chown -R kolab-n:kolab-n horde framework imp kronolith mnemo nag passwd turba ingo
+# mv horde /kolab/var/kolab/www/
+# mv imp kronolith mnemo nag passwd turba ingo /kolab/var/kolab/www/horde/
+</pre>
+
+<h4>Step 7</h4>
+
+<p>Install the Horde schema into OpenLDAP. This schema allows Horde preferences
+to be stored in each Kolab user's object within LDAP. Add the following to your
+<code>/kolab/etc/kolab/slapd.conf.template</code> after the existing
+schema include lines:</p>
+
+<pre>
+include /kolab/var/kolab/www/horde/scripts/ldap/horde.schema
+</pre>
+
+<p>Save the template and run <code>kolabconf</code> to update OpenLDAP to
+use the new schema file.</p>
+
+<h4>Step 8</h4>
+
+<p>Set up the Horde database in MySQL. This database is used to store general
+Horde information, as well as per-user settings such as category information, etc.
+You can also view these instructions in the <code>horde/scripts/db/README</code> file.</p>
+
+<p>You should first edit <code>/kolab/var/kolab/www/horde/scripts/db/mysql_create.sql</code>
+and change the Horde MySQL user password to something more secure. The section you need to
+edit looks like this:</p>
+
+<pre>
+REPLACE INTO user (host, user, password)
+ VALUES (
+ 'localhost',
+ 'horde',
+-- IMPORTANT: Change this password!
+ PASSWORD('horde')
+ );
+</pre>
+
+<p>Now add the Horde database:</p>
+
+<pre>
+# mysql --user=root --password=<b>your-mysql-root-pw</b> < /kolab/var/kolab/www/horde/scripts/db/mysql_create.sql
+# mysqladmin --user=root --password=<b>your-mysql-root-pw</b> reload
+</pre>
+
+<p>To check that this is working, the following command should execute
+without errors:</p>
+
+<pre>
+# mysql --user=horde --password=<b>your-horde-user-pw</b> horde
+</pre>
+
+<h4>Step 9</h4>
+<p>You now need to configure all the Horde applications. Log in to your Horde
+installation, at http://your.kolab.server/horde/.</p>
+
+<ul>
+<li>Click on 'Administration', then 'Configuration'. You should see a list
+of available Horde applications.</li>
+<li>Go through this list and configure each Horde application as you please.
+You may want to choose 'Logout' in the 'Select any applications
+that should be linked in XXX's menu' section for each application's configuration,
+so that there is a 'Logout' menu option on the top menu for each application.
+The following configuration options should be adhered to for each application:</li>
+</ul>
+
+<dl>
+<di>Address Book (turba)</di>
+<dd>The default configuration should prove sufficient.</dd>
+
+<di>Calendar (kronolith)</di>
+<dd>Select the 'Kolab' driver for both the 'Calendar' and 'Free/Busy' sections.</dd>
+
+<di>Filters (ingo)</di>
+<dd>The default configuration should prove sufficient.</dd>
+
+<di>Horde (horde)</di>
+<dd><ul><li>Select the 'Kolab' tab and configure each entry to the values pertaining to
+your specific kolab server.</li>
+<li>Under the 'Database' tab, be sure to set the 'password'
+field to whatever you specified when creating the Horde database in MySQL.</li>
+<li>In the 'Authentication' tab, select 'IMAP' as the authentication backend.
+Change the 'Configration type' to 'Separate Values', and set the 'Connection Protocol'
+to 'imap/notls/novalidate-cert'. You may also want to specify a Kolab account in the
+'Administrators' field, for use in configuring Horde at a later stage. If you have a
+Kolab account such as <code>horde-admin at my.kolab.domain</code>, enter it here.</li>
+<li>(Optional) Under the 'Logging' tab, change the 'Path to the log file' to
+<code>/kolab/var/horde/horde.log</code>. For this to work you'll have to do the following:
+<pre>
+# mkdir -p /kolab/var/horde/
+# chown kolab-n:kolab-n /kolab/var/horde/
+</pre>
+</li>
+<li>Under the 'Preference System' tab, select 'LDAP' as the preferences driver, and enter the
+following values for each field (mirroring those specified under the 'Kolab' tab):<br />
+Base DN -> The same as Kolab\Base DN<br />
+DN of the root account -> The same as Kolab\Manager DN<br />
+Root DN password -> The same as Kolab\Manager Password<br />
+Username search key -> 'mail'
+</li>
+<li>Under the 'Mailer' tab, select SMTP as the mail send method.</li>
+</ul>
+</dd>
+
+<di>Mail (imp)</di>
+<dd>Make sure the botton two options are checked on the 'Custom Hooks' tab.
+You may also want to specify the location of the ispell or aspell binary,
+if you have one of these installed, in the 'External Utilities and Menu'
+tab in order to allow users to spellcheck their email.</dd>
+
+<di>Notes (mnemo)</di>
+<dd>Select the 'Kolab' driver under the 'Storage System' section.</dd>
+
+<di>Password (passwd)</di>
+<dd>Uncheck the option entitled 'Should we allow the user to specify the
+username?'.</dd>
+
+<di>Tasks (nag)</di>
+<dd>Select the 'Kolab' driver under the 'Storage System' section.</dd>
+</dl>
+
+<h4>Conclusion</h4>
+<p>*phew* That's it! You should now be able to log in to the webclient
+with any Kolab user. Quite a procedure to set it up, but I think you'll find it's worth it.
+We've put a lot of effort into the Webclient and as the current clients go,
+we'd like to think it's the best in terms of features :-) This guide is
+meant to tide users over until Horde releases their next stable version,
+at which time we can freeze the code and create an OpenPKG-compatible RPM
+that will greatly simplify this process of installing the webclient. Hang on
+till then!</p>
+
+<a name="opa"><h4>Appendix A</h4></a>
+
+<p>The OPA script; this should be put in your <code>~/.bashrc</code> or similar
+shell startup file.</p>
+
+<pre>
+opa () {
+ root="$1"
+ if [ ! -d $root ]; then
+ echo "opa:ERROR: OpenPKG root directory $root not found"
+ return 1
+ fi
+ if [ ! -f "$root/etc/rc" ]; then
+ echo "opa:ERROR: does not contain OpenPKG hierarchy"
+ return 1
+ fi
+ eval `$root/etc/rc --eval all env`
+}
+</pre>
+
+<a name="obmconf"><h4>Appendix B</h4></a>
+
+<p>This <code>obmtool.conf</code> file can be used to install a Horde-ready Kolab installation
+based on OpenPKG 2.0.</p>
+
+<pre>
+##
+## obmtool.conf -- OpenPKG poor man's Boot, Build & Management Tool Configuration
+## based on Ralf S. Engelschall's "obmtool.conf -- Development Tool Configuration"
+## Copyright (c) 2003 Thomas Lotterer <thomas at lotterer.net>
+##
+
+%common
+ @hasfeature TAGFMT || exit # require obmtool to support TAGFMT
+ TMPDIR=/ltmp # large tmp with 300MB space
+ URL="ftp://ftp.zfos.org/brew/kolab/SRC" # used for non-ftp://ftp.openpkg.org/ packages
+
+%kolab
+ echo "---- boot/build ${NODE} %${CMD} ----"
+ PREFIX=/${CMD};
+ loc='./' # '' (empty) for ftp.openpkg.org, '=' for URL, './' for CWD or absolute path
+ pls=${loc:-+}
+ with_genuine=no
+
+ # start from scratch or upgrade within 2.0.x
+ @install openpkg-2.0.0-2.0.0 \
+ --tag="zfos" \
+ --prefix="${PREFIX}" \
+ --user="${CMD}" --group="${CMD}" \
+ --muid="19414" --ruid="19415" --nuid="19416" \
+ --mgid="19414" --rgid="19415" --ngid="19416"
+ @install ${loc}make-3.80-2.0.0
+ @install ${loc}binutils-2.14-2.0.0
+ @install ${loc}gcc-3.3.3-2.0.0
+ @install ${loc}fsl-1.4.0-2.0.0
+ @install ${loc}mm-1.3.0-2.0.0
+ @install ${loc}perl-5.8.3-2.0.0
+ @install ${loc}perl-openpkg-5.8.3-2.0.0
+ @install ${loc}perl-conv-5.8.3-2.0.0
+ @install ${loc}readline-4.3.5-2.0.0
+ @install ${loc}sharutils-4.2.1-2.0.0
+ @install ${loc}ncurses-5.4.20040214-2.0.0
+ @install ${loc}perl-term-5.8.3-2.0.0
+ @install ${loc}perl-ds-5.8.3-2.0.0
+ @install ${loc}perl-util-5.8.3-2.0.0
+ @install ${loc}perl-mail-5.8.3-2.0.0
+ @install ${loc}perl-crypto-5.8.3-2.0.0
+ @install ${loc}perl-net-5.8.3-2.0.0
+ @install ${loc}zlib-1.2.1-2.0.0
+ @install ${loc}expat-1.95.7-2.0.0
+ @install ${loc}perl-xml-5.8.3-2.0.0
+ @install ${loc}perl-www-5.8.3-2.0.0
+ @install ${loc}perl-time-5.8.3-2.0.0
+ @install ${loc}openssl-0.9.7c-2.0.0
+ @install ${loc}imap-2004rc6-2.0.0
+ @install ${loc}perl-ssl-5.8.3-2.0.0
+ @install ${loc}procmail-3.22-2.0.0
+ @install ${loc}db-4.2.52.2-2.0.0
+ @install ${loc}openldap-2.2.5-2.0.0
+ @install ${loc}sasl-2.1.17-2.0.0 --with=ldap --with=login
+ @install ${loc}getopt-20030307-2.0.0
+ @install ${loc}proftpd-1.2.9-2.0.0 --with=ldap
+ @install ${loc}pcre-4.5-2.0.0
+ @install ${loc}gdbm-1.8.3-2.0.0
+ @install ${pls}dbtool-1.6-2.0.0
+ @install ${loc}postfix-2.0.18-2.0.0 --with=ldap --with=sasl --with=ssl
+ @install ${loc}perl-sys-5.8.3-2.0.0
+ @install ${loc}perl-ldap-5.8.3-2.0.0
+ if [ ".${with_genuine}" = .no ]; then
+ @install ${loc}perl-db-5.8.3-2.0.0
+ @install ${pls}perl-kolab-5.8.3-2.0.0
+ fi
+ @install ${pls}imapd-2.2.3-2.0.0 --with=group
+ @install ${loc}m4-1.4o-2.0.0
+ @install ${loc}bison-1.35-2.0.0
+ @install ${loc}flex-2.5.4a-2.0.0
+ @install ${loc}libiconv-1.9.2-2.0.0
+ @install ${loc}gettext-0.14.1-2.0.0
+ #install ${loc}openpkg-tool-FIXME
+ @install ${loc}patch-2.5.9-2.0.0
+ @install ${loc}sed-4.0.9-2.0.0
+ @install ${loc}libxml-2.6.6-2.0.0
+ @install ${loc}libxslt-1.1.3-2.0.0
+ @install ${loc}mysql-4.0.18-2.0.0
+ @install ${loc}apache-1.3.29-2.0.0 \
+ --with=mod_auth_ldap \
+ --with=mod_dav \
+ --with=mod_php \
+ --with=mod_php_gdbm \
+ --with=mod_php_gettext \
+ --with=mod_php_imap \
+ --with=mod_php_openldap \
+ --with=mod_php_pear \
+ --with=mod_php_xml \
+ --with=mod_ssl \
+ --with=mod_php_dom \
+ --with=mod_php_mysql
+ if [ ".${with_genuine}" = .no ]; then
+ @install ${pls}kolab-20040217-2.0.0 --without=genuine
+ else
+ @install ${pls}kolab-20040217-2.0.0 --with=genuine
+ fi
+ @check
+
+%dump
+ echo "PRG = \"$PRG\""
+ echo "CMD = \"$CMD\""
+ echo "URL = \"$URL\""
+ echo "TRACK = \"$TRACK\""
+ echo "EGREP = \"$EGREP\""
+ echo "CHECKONLY = \"$CHECKONLY\""
+ echo "ERASESURPLUS = \"$ERASESURPLUS\""
+ echo "HASX11 = \"$HASX11\""
+ echo "PREFIX = \"${PREFIX}\""
+ echo "ARCH = \"${ARCH}\""
+ echo "OS = \"${OS}\""
+ echo "TAG = \"${TAG}\""
+ echo "TMPDIR=\"${TMPDIR}\""
+</pre>
m4_include(footer.html.m4)
More information about the commits
mailing list