[commits] [Wiki] changed: FAQ/Admin/Install
Jan Schneider
jan at horde.org
Thu Apr 28 12:17:27 UTC 2011
jan Thu, 28 Apr 2011 12:17:27 +0000
Modified page: http://wiki.horde.org/FAQ/Admin/Install
New Revision: 2.0
Change log: Remove old stuff, update for Git
@@ -5,15 +5,17 @@
[[toc]]
+++ Where can I obtain Horde and its components?
-Go to our [http://www.horde.org/download/ Download Page].
+**[Horde 4]:** Horde 4 and later is distributed through the PEAR
installer. See the
[http://www.horde.org/apps/horde/docs/INSTALL#installing-with-pear
installation documentation] for details.
-All components which have never seen a stable release are available
through CVS. [http://www.horde.org/source/using.php Step-by-step
directions] for obtaining them with CVS are available on the Horde
website.
+**[Horde 3]:** Go to our [http://www.horde.org/apps Download Page].
+
+All components which have never seen a stable release are available
through Git (CVS for Horde 3). [http://www.horde.org/development
Step-by-step directions] for obtaining them with Git or CVS are
available on the Horde website.
(Please keep in mind that anything that hasn't seen a stable release
hasn't seen it for a reason; while some of the components are
functional at this point and may be capable of being used in
production, they're still not quite ready in the eyes of the
developers, and might be buggy in interesting and well-hidden ways.)
-Nightly snapshots of all CVS modules are also available at
[http://snaps.horde.org/ Snapshot site] in tar formats. Since these
are unattended, automatted snapshots they may not always be stable or
even work at all. They are mostly intended for those who need the CVS
code but do not have access to CVS.
+Nightly snapshots of all modules are also available at
[http://snaps.horde.org/ Snapshot site] in tar formats. Since these
are unattended, automatted snapshots they may not always be stable or
even work at all. They are mostly intended for those who need the
latest development code but do not have access to Git resp. CVS.
+++ What version of Horde should I be using?
See [http://www.horde.org/source/versions.php Horde Version Compatibility].
@@ -25,104 +27,21 @@
+++ Can I install Horde and its components as precompiled packages?
On some Linux distributions, it is possible to install Horde and any
of its stable components from precompiled packages.
-The Horde Project no longer makes our own RPMs available (old
packages can be found [ftp://ftp.horde.org/pub/RPMS/ here]).
+The Horde Project no longer makes our own distribution packages available.
Debian users can install IMP through their package manager as well;
the IMP packages are available in the
[http://packages.debian.org/stable/web/imp4 stable distribution].
-++++ How can I make Debian's PHP package use IMAP-SSL?
-
-##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):
-
-<code>
-mkdir /usr/local/src
-cd /usr/local/src
-</code>
-
-Get the source to the PHP IMAP package (you must have {{deb-src:}}
lines in your {{/etc/apt/sources.list}} for this to work)
-
-<code>
-apt-get source php4-imap
-</code>
-
-This will download and unpack the source to the php4 package.
-
-Make sure that you have all the development tools necessary to build
the php4 package. A list of them can be found in
{{/usr/local/src/php4_VERSION.dscM}}. Install all of those packages
with {{apt-get}}. Make sure to use {{libc-client-ssl2000}} and
{{libc-client-ssl2000-dev}} (in {{non-us}}) instead of plain
{{libc-client}}.
-
-Move into the source tree unpacked by Debian:
-
-<code>
-cd /usr/local/src/php4-VERSION/debian
-</code>
-
-Make these two changes: in the file rules, add the line
-
-<code>
---with-imap-ssl \
-</code>
-
-directly under the line
-
-<code>
---with-imap=shared \
-</code>
-
-and in the file {{libc-client.la}}, change the line
-
-<code>
-dependency_libs=' -lpam -ldl -lcrypt'
-</code>
-
-to read
-
-<code>
-dependency_libs=' -lpam -ldl -lcrypt -lc-client -lssl -lcrypto'
-</code>
-
-(and in case you're wondering, the added flags are given in
{{/usr/share/doc/libc-client-ssl2000-dev/README.Debian}}).
-
-Then move into the root of the unpacked source directory:
-
-<code>
-cd /usr/local/src/php4-VERSION
-</code>
-
-and build the package (the {{-us -uc}} options prevent you from
trying to cryptographically sign the binaries):
-
-<code>
-dpkg-buildpackage -us -uc -rsudo
-</code>
-
-You can also use {{-rfakeroot}}, or whatever your favorite root enabler is.
-
-Wait for the compile to finish. If it doesn't work, make sure you've
installed all the devel packages you need, and then start making burnt
offerings.
-
-When the compile succeeds, move up to the root level of the source:
-
-<code>
-cd /usr/local/src
-</code>
-
-and then install all of the new debs that you've created. Note that
you //must// install the new {{php4-VERSION.deb}} that is built, as
all the modules are compiled against it. You cannot mix your
newly-compiled php4 with any existing modules from the debian package
system. So if you already have php4, php4-gd, and php4-imap on your
system from Debian, you have to install php4, php4-gd, and php4-imap
from your new source directory for everything to continue working. In
the example above, you'd say (as root):
-
-<code>
-dpkg -i php4_VERSION.deb php4-imap_VERSION.deb php4-gd_VERSION.deb
-</code>
-
-Once that's all done, restart the webserver, and see if SSL works!
++++ How do I install from Git?
-//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.
+[http://www.horde.org/development/git Step-by-step directions] for
obtaining the software with Git are available on the Horde website. In
addition, please note the following issues which often come up:
-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.
+* After some Git 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 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:
+[http://www.horde.org/development/cvs 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.
* 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.
More information about the commits
mailing list