\documentclass{article}
\usepackage{ulem}
\pagestyle{headings}
\begin{document}
\part{Overview}
This component delivers a small subset of the functionality required to deal with the data structures established by the PEAR project\footnote{http://pear.php.net}. Currently it allows accessing the REST interface of a remote PEAR server and provides utilities to deal with package.xml files. The most important functionality concerning the packaging manifest is the automatic update of the XML data.

Further details can be found in the accompanying documents REMOTE\_PEAR\_SERVER\footnote{http://example.com/index.php?page=Doc/Dev/HordePear/REMOTE\_PEAR\_SERVER} and PACKAGE\_XML\footnote{http://example.com/index.php?page=Doc/Dev/HordePear/PackageXml}.

\part{Rationale for this component}
This package reimplements some of the code that is being provided on pear.php.net\footnote{http://pear.php.net} via various PEAR\_* packages.

Of course it should not be necessary to write new code providing PEAR functionality given the available PEAR\_* packages. Unfortunately none of these provide anything near a decent and usable developer API. One could hope for the newer Pyrus\footnote{http://pear2.php.net/} code to resolve some of the deeper structural problems the PEAR code has. The currently available code (as of 2011) does not look like a major improvement though.

The decision to reimplement PEAR code has not been taken lightly: originally the Horde components helper had been using the PEAR code. But the amount of hacks and workarounds required to sustain that basis was too much for a long term solution. As a consequence Horde\_Pear was started in order to generate a backend providing the functionality specifically required by the Horde components helper.

\end{document}
