cvs: peardoc /en/chapters faq.xml

arnaud Fri Aug 15 17:15:54 2003 EDT Modified files: /peardoc/en/chapters faq.xml Log: * ws Index: peardoc/en/chapters/faq.xml diff -u peardoc/en/chapters/faq.xml:1.6 peardoc/en/chapters/faq.xml:1.7 --- peardoc/en/chapters/faq.xml:1.6 Tue Jun 17 06:22:41 2003 +++ peardoc/en/chapters/faq.xml Fri Aug 15 17:15:54 2003 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.6 $ --> +<!-- $Revision: 1.7 $ --> <!-- [mj] The FAQ needs some heavy revision - don't translate it right now --> <chapter id="faq"> @@ -49,7 +49,7 @@ whatever the right name is. </para> </sect1> -<!-- +<!-- <sect1 id="faq.install-pecl"> <title> How do I install a PECL module written in C? @@ -85,7 +85,7 @@ </listitem> <listitem> <simpara> - make + make </simpara> </listitem> <listitem> @@ -160,7 +160,7 @@ <filename>pear/</filename> is based on what package the files belong to. Where files are located in each package directory is completely independent from where they end up being installed, - this is all determined by the package description file. + this is all determined by the package description file. </para> </sect1> @@ -293,7 +293,7 @@ There is no problem with competitive packages, but we want to avoid pollution with 10 template classes, 7 different mail classes, and 3 different layers for databases doing the same only with - different function names. + different function names. </simpara> <para> First of all, do a reality check: Why do I want to commit a new @@ -301,7 +301,7 @@ PEAR</quote> or <quote>I didn't understand the API of the existing class</quote>. </para> - <para> + <para> A good reason for a new class is often, that you are missing a function, behaviour or speed in an existing implementation. In this case, you should take a look at this class, if it possible @@ -323,7 +323,7 @@ url="mailto:&email.pear.dev;">PEAR developers mailinglist</ulink>! </para> </sect1> - + <sect1 id="faq.question"> <title> I have a question about PEAR. Where should I ask? @@ -366,7 +366,7 @@ <para> On all mailing lists mentioned above the language is english and the way you ask questions should always be polite :-). - </para> + </para> </sect1> <sect1 id="faq.require"> @@ -394,7 +394,7 @@ To make PEAR work on Windows, you simple need to add the PEAR installation dir (e.g. <filename>c:\php\pear</filename>) to the include_path directive in your <filename>php.ini</filename>. - </para> + </para> <simpara> Note: There are some classes (like Schedule/At.php), that do not work on Windows, because they use *nix specific commands. @@ -413,14 +413,14 @@ </simpara> <para> - To make it short: Any Open Source/Free Software License. See the + To make it short: Any Open Source/Free Software License. See the <ulink url="&url.license.opensource;"> - OSI Approved Licenses</ulink> for a summary of Open Source + OSI Approved Licenses</ulink> for a summary of Open Source licenses and <ulink url="&url.license.gnu;"> FSF Approved Licenses</ulink>. Pick one that appears on both lists. It - does not need to be a GPL-compatible license from the FSF list. Here are - a subset of the licenses that are on both lists: - Apache License, + does not need to be a GPL-compatible license from the FSF list. Here are + a subset of the licenses that are on both lists: + Apache License, Artistic license, BSD license, Common Public License, @@ -444,8 +444,8 @@ </para> <para> - The recomended licenses are - <ulink url="&url.license.php;">PHP</ulink>, + The recomended licenses are + <ulink url="&url.license.php;">PHP</ulink>, <ulink url="&url.license.lgpl;">LGPL</ulink> and <ulink url="&url.license.bsd;">BSD</ulink> style. @@ -463,7 +463,7 @@ <para> To set the license of you PEAR/PECL package, put it in the head of all source code files of your package and also the type of it - inside the &lt;license&gt; tag of your package description file + inside the &lt;license&gt; tag of your package description file (<filename>package.xml</filename>). </para> </sect1>