[cvs] [Wiki] changed: FAQ/Admin/Install

[Jan Schneider]

jan  Sat, 29 Apr 2006 02:56:35 -0700

Modified page: http://wiki.horde.org/FAQ/Admin/Install
New Revision:  1.5
Change log:  Style

@@ -35,9 +35,9 @@
 ##red|These instructions are quite old.##
 
 [mailto:jhealy at logn.net Jason Healy] contributed these instructions for building PHP with IMAP-SSL support. He tested them on a Debian testing system (Woody) with PHP 4.0.5-2.
 
-Find a nice quiet directory (replace /usr/local/src or your favorite source tree location:):
+Find a nice quiet directory (replace {{/usr/local/src}} or your favorite source tree location):
 
 <code>
 mkdir /usr/local/src
 cd /usr/local/src
@@ -70,9 +70,9 @@
 <code>
 --with-imap=shared \ 
 </code>
 
-and in the file libc-client.la, change the line
+and in the file {{libc-client.la}}, change the line
 
 <code>
 dependency_libs=' -lpam -ldl -lcrypt'
 </code>
@@ -114,18 +114,18 @@
 </code>
 
 Once that's all done, restart the webserver, and see if SSL works!
 
-//NOTES//: If the compile breaks, check the package dependencies in the .dsc file and make sure you have them installed correctly. Also, make sure that the flags you add to the libc-client.la file match those specified in the libc-client-ssl README.
+//NOTES//: If the compile breaks, check the package dependencies in the .dsc file and make sure you have them installed correctly. Also, make sure that the flags you add to the {{libc-client.la}} file match those specified in the libc-client-ssl README.
 
 If your webserver refuses to restart, it's probably because you're mixing old and new PHP modules. You cannot just replace the IMAP module with your new compiled version; you must use your newly compiled php4 base, plus ALL the modules you compiled that match those already on your system. {{dpkg -i}} should replace the modules on your system with the newly compiled ones without causing any dependency problems.
 
 +++ How do I install from CVS?
 
 [http://www.horde.org/source/using.php Step-by-step directions] for obtaining the software with CVS are available on the Horde website. In addition, please note the following issues which often come up:
 
 * When updating via CVS, it is critical that you watch for //Conflicts// as noted by the //C// flag in the output. Any conflicts must be resolved by manually editing the file.
-* When updating via CVS, make sure you check for any configuration files (config/*.php.dist or config/*.xml) which have been modified. You will need to manually merge any changes to these files into your working configuration files.
+* When updating via CVS, make sure you check for any configuration files ({{config/*.php.dist}} or {{config/*.xml}}) which have been modified. You will need to manually merge any changes to these files into your working configuration files.
 * Before reporting an error with a CVS version of some software, make sure you have updated it so that you don't report errors which have already been fixed.
 * After some CVS updates, you may have to logout of your session, restart your browser, or even restart your web server for the changes to be seen.
 
 +++ How do I upgrade via patch files?
@@ -156,9 +156,9 @@
 </code>
 
 See {{po/README}} for details.
 
-As the upgrade process does not change your configuration files, but rather only operates on the *.php.dist files in the configuration directories. So you will need to manually compare your configuration files to their respective *.dist version, and merge in any changes or additions needed.
+As the upgrade process does not change your configuration files, but rather only operates on the {{*.php.dist}} files in the configuration directories. So you will need to manually compare your configuration files to their respective {{*.dist}} version, and merge in any changes or additions needed.
 
-Be sure to check for a file called docs/UPGRADING or docs/UPDATE for additional information such as updates to database layouts or other changes which may be needed. This file will not always exist (if no additional steps are needed when upgrading) so don't panic if it isn't there!
+Be sure to check for a file called {{docs/UPGRADING}} or {{docs/UPDATE}} for additional information such as updates to database layouts or other changes which may be needed. This file will not always exist (if no additional steps are needed when upgrading) so don't panic if it isn't there!
 
 If you shut down your web services, then restart them at this point. Even if you did not shut down your services before the upgrade, in some cases you may need to restart your web server at this point anyway.