initial commit

Package-Manager: portage-2.2.0_alpha166
RepoMan-Options: --force

www-apps/zarafa-sabre/files/postinstall-en.txt

@@ -0,0 +1,25 @@
+------------------------------------------------------------------------
+INSTALLATION
+
+
+Edit config.inc.php to setup your domain name. This should work without setting it but it is better for SabreDAV to work. 
+You can also adjust other settings, some are highly experimentals (non utf8 vcards for instance) and should be used only for testing.
+
+You then need to redirect all requets to server.php. To do this you can use mod_rewrite:
+
+<Directory /var/www/${VHOST_HOSTNAME}/zarafa-sabre>
+                DirectoryIndex server.php
+                RewriteEngine On
+                RewriteBase /zarafa-sabre
+                RewriteCond %{REQUEST_FILENAME} !-f
+                RewriteCond %{REQUEST_FILENAME} !-d
+                RewriteRule ^.*$ /zarafa-sabre/server.php
+</Directory>
+
+Please note that the authentification backend use Basic auth. Some clients will only work with Basic auth if the host use SSL.
+
+Some detailed information about SabreDAV setup are available in SabreDAV documentation. Do not hesitate to read it!
+
+Finally you should be able to log in to Sabre-Zaraf at
+
+http://${VHOST_HOSTNAME}/zarafa-sabre

www-apps/zarafa-sabre/files/postupgrade-en.txt

@@ -0,0 +1,13 @@
+------------------------------------------------------------------------
+UPGRADE
+
+Upgrading to a newer Sabre-Zarafa version follows the same path as the initial 
+installation.
+
+When upgrading to a new minor version e.g. from Sabre-Zarafa 0.15.1 to Sabre-Zarafa 0.15.2, 
+the existing Sabre-Zarafa directory can be overwritten when extracting the archive.
+When installing a new major version it is recommended to extract the tarball 
+to another directory and to copy the state from the existing installation.
+
+Please also observe the published release notes of the new Sabre-Zarafa version.
+For some releases it is necessary to e.g. resynchronize the mobile.