<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -1,5 +1,7 @@
 2008-06-23  Gunnar Wrobel  &lt;p@rdus.de&gt;
 
+	* INSTALL: Update the install instructions.
+
 	* modules/tool_pardalys/manifests/init.pp: Add p@rdalys
 	configuration files for slave servers.
 </diff>
      <filename>pardalys/ChangeLog</filename>
    </modified>
    <modified>
      <diff>@@ -32,7 +32,7 @@ to put your public SSH key on github.com for this to work).
 After that you can start modifying the sources and commit to your
 fork. Once you are pleased with the results you may send a pull requst
 to the main repository on github.com. If your changes have the
-required quality they might get integrated in the main repository.
+required quality they will get integrated in the main repository.
 
 
 Changes</diff>
      <filename>pardalys/HACKING</filename>
    </modified>
    <modified>
      <diff>@@ -19,13 +19,63 @@ Prerequisites
   p@rdalys requires the following to work:
 
     - &gt;=puppet-0.24.5 (http://reductivelabs.com/trac/puppet)
+    - ruby-ldap (http://ruby-ldap.sourceforge.net/)
 
-  Puppet should also support LDAP (meaning ruby-ldap needs to be
-  installed).
 
+Installing the software on Gentoo
+---------------------------------
 
-Installing the software
------------------------
+The primary focus of p@rdalys is Gentoo and installation is automated
+on this platform.
+
+  1) Install the kolab overlay
+
+     You can install the overlay by running:
+
+       layman -f -a kolab
+
+     Currently p@rdalys is still purely experimental and not
+     maintained within the main Gentoo portage tree. The package
+     definitions are only available via the Kolab overlay at the
+     moment.
+
+  2) Unmask the package
+
+     Tell portage to accept the experimental packages by running:
+
+       echo &quot;app-admin/pardalys&quot; &gt;&gt; /etc/portage/package.unmask
+       echo &quot;app-admin/pardalys ~x86&quot; &gt;&gt; /etc/portage/package.keywords
+       echo &quot;app-admin/puppet ~x86&quot; &gt;&gt; /etc/portage/package.keywords
+       echo &quot;dev-ruby/facter ~x86&quot; &gt;&gt; /etc/portage/package.keywords
+
+     As mentioned above the package is still experimental. As it is
+     still masked you need to unmask it and accept the unstable
+     keyword on the package.
+
+     p@rdalys depends on puppet and puppet in turn depends on
+     facter. Both packages are still marked unstable and need to be
+     accepted in that form.
+
+  3) Install the package
+
+     Now you can run emerge to install the package:
+
+       emerge pardalys
+
+     If you want to use p@rdalys in developers mode you should ensure
+     that you activated the &quot;develop&quot; USE flag for this package.
+
+  Optional:
+  ~~~~~~~~~
+
+   - Switching to developers mode
+
+     You can easily switch to p@rdalys developers mode. Refer to the
+     instructions in the HACKING file in this directory.
+
+
+Installing the software on other systems
+----------------------------------------
 
   Download the package, unpack it and include the unpacked &quot;modules&quot;
   directory in your puppet modules.
@@ -34,8 +84,49 @@ Installing the software
 Configuring the software
 ------------------------
 
-  Nothing yet.
+  1) Edit /etc/kolab/kolab.bootstrap
+
+
+  Optional:
+  ~~~~~~~~~
+
+   - Embedding a host in an already existing Kolab network
+
+     If you run a network of Kolab hosts you will have a central LDAP
+     master server. Your initial setup for a new host requires the
+     following steps:
+
+       mkdir /etc/pardalys
+
+     This creates an alternative p@rdalys configuration
+     directory. First we copy the default configuration:
+
+       cp /usr/share/pardalys/etc/puppet.conf /etc/pardalys/
+
+         or
+
+       cp /usr/share/pardalys/dev-pardalys/pardalys/etc/puppet.conf /etc/pardalys/
+
+     Now add the details for the LDAP master server to the copied
+     file. The followin assumes the master cares for the domain
+     example.com and is named smtp.example.com:
+
+       node_terminus = ldap
+       ldapserver = smtp.example.com
+       ldapbase = dc=example,dc=com
+       ldapstackedattrs = puppetvar
+       ldapuser = cn=nobody,cn=internal,dc=example,dc=com
+       ldappassword = xyz
+
+     Copy the parameters ldap_master_uri, ldap_uri, base_dn, bind_dn,
+     bind_pw, bind_pw_hash, bind_dn_restricted, bind_pw_restricted
+     from /etc/kolab/kolab.conf on your master server to
+     /etc/kolab/kolab.bootstrap on your slave host.
+     (FIXME: This should be easier!)
+
+     Now run p@rdalys to setup the new host:
 
+       pardalys
 
 Upgrading the software
 ----------------------</diff>
      <filename>pardalys/INSTALL</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>ffe2aa9d4f24f22ac86eba6f38f30a71dfc06720</id>
    </parent>
  </parents>
  <author>
    <name>Gunnar Wrobel</name>
    <email>p@rdus.de</email>
  </author>
  <url>http://github.com/wrobel/pardalys/commit/f57d85ac3c8fc92cefc6bce8759b098f4046d5a3</url>
  <id>f57d85ac3c8fc92cefc6bce8759b098f4046d5a3</id>
  <committed-date>2008-06-23T03:33:22-07:00</committed-date>
  <authored-date>2008-06-23T03:33:22-07:00</authored-date>
  <message>Update the install instructions.</message>
  <tree>04174f680e5b4be99371916f655d2a87182e4512</tree>
  <committer>
    <name>Gunnar Wrobel</name>
    <email>p@rdus.de</email>
  </committer>
</commit>
