php-src/pear
Sascha Schumann 876bac4823 builddir is used by the Unix build framework.
Rename builddir to phpbuilddir
2000-08-24 12:02:05 +00:00
..
PEAR @Added XML_Parser class in PEAR (Stig) 2000-07-30 17:41:31 +00:00
tests @Added XML_Parser class in PEAR (Stig) 2000-07-30 17:41:31 +00:00
DB.php -Add getCode() method to PEAR_Error 2000-08-24 01:34:16 +00:00
HTTP.php various version 2.0 and 2.01 licenses -> 2.02 2000-07-24 05:41:02 +00:00
install-pear.txt Complain loudly, if we were not able to install everything. 2000-05-02 22:28:12 +00:00
Makefile.in builddir is used by the Unix build framework. 2000-08-24 12:02:05 +00:00
package.dtd * the beginning of a regression testing framework? 2000-07-25 00:55:37 +00:00
pear.in * generate pear scripts properly with configure 2000-07-24 23:55:34 +00:00
pear.m4 Use the new PHP_GEN_* macros in pear 2000-06-14 06:30:14 +00:00
PEAR.php.in -Add getCode() method to PEAR_Error 2000-08-24 01:34:16 +00:00
php-config.in * generate pear scripts properly with configure 2000-07-24 23:55:34 +00:00
phpextdist Added phpextdist script for making external extension packages. 2000-02-22 14:26:12 +00:00
phpize.in Relicense build-related files under the PHP License 2000-08-20 05:36:07 +00:00
README * PEAR now stands for "PHP Extension and Application Repository" 2000-07-28 21:05:00 +00:00
run-tests.in @Added XML_Parser class in PEAR (Stig) 2000-07-30 17:41:31 +00:00
TODO added TODO file for PEAR 2000-07-24 13:32:50 +00:00

	   PEAR - PHP Extension and Application Repository
	   ===============================================
	     Dedicated to Malin Bakken, born 1999-11-21

WHAT IS PEAR?

PEAR is a code repository for PHP extensions and PHP library code
similar to TeX's CTAN and Perl's CPAN.

The intention behind PEAR is to provide a means for library code
authors to organize their code in a defined way shared by other
developers, and to give the PHP community a single source for such
code.


ADMINISTRATION

This section will describe the rules for how files are structured and
how functions and classes should be named.


TOOLS

This section will describe the tools provided to PEAR users.


CODING RULES AND GUIDELINES

* All PHP code must use <?php ?>.  This is the only really portable tag.

* Before adding a new top-level directory ("DB" is one), discuss your
  intentions on php-pear@lists.php.net.