PHP Manual

PEAR Manual

Smarty Manual

PostgreSQL

MySQL Manual

Perl Manual

podręcznik pear
poprzedninastępny

rozdział 1. introduction

spis treści
what is pear?
the pear manifest

pear is dedicated to malin bakken, born 1999-11-21.

what is pear?

pear is short for "php extension and application repository" and is pronounced just like the fruit. the purpose of pear is to provide:

pear is a community-driven project with the pear group as the governing body. the project has been founded by stig s. bakken in 1999 and quite a lot of people have joined the project since then.

structured library of php code

the code in pear is partitioned in "packages". each package is a separate project with its own development team, version number, release cycle, documentation and a defined relation to other packages (including dependencies). packages are distributed as gzipped tar files with a description file inside, and installed on your local system using the pear installer.

there are two types of packages: source packages (containing source files only), and binary packages (containing platform-specific binary files, and possible source files). installing source packages with c code obviously requires a c build environment.

pear defines a package tree, where each "node" in the tree is represented by a part of the package name. the nodes are organized by simple descriptive topics, and each part is separated by an underscore. examples of package names are "mp3_id", "archive_tar" and "http_post".

packages may relate to each other through explicit dependencies, but there is no automatic relation between for example a package and its "parent" in the package tree (for example, "http_post" is by default independent of "http").

a few top-level nodes in the package tree called "sub-repositories" have special functions, currently these are pecl and gtk. for each of these, different rules apply, see more in the description of each sub-repository below.

a style guide, the pear coding standards (short pcs), exists to ease collaboration between pear developers, to help quality and portability, and to help pear contributors to provide consistent-looking-and-feeling apis.

code distribution and package maintenance

all pear packages are registered in and uploaded to a central database available at pear.php.net. open-sourced third-party packages may also be registered and uploaded. closed-source packages may be installed by the pear installer, but the pear database is for open-source code only.

pear.php.net will provide both a human-friendly (html) and machine-friendly (currently xml-rpc) interface to the pear database. package downloads are done with plain http. other functions the pear.php.net site will provide are:

packages are distributed as a gzipped tar file with an xml description file inside. the description file contains some information about the package, a list of files and their roles, and dependencies.

the php extension community library (pecl)

pecl

pecl (pronounced "pickle") used to be a sub-repository of pear for c extensions "à la" those distributed with php 4, in fact, having somewhere to move extensions to from php was one of the motivations when creating pecl. extensions in pecl follow php's coding standards rather than pear's, but they are distributed and installed as pear packages.

the process of moving an extension from php to pecl is referred to as "pickling".

in october 2003 pecl has become an independent project, which does not belong to pear anymore. (except for the infrastructure, which pecl borrows from pear.) more information and all pecl packages can now be found on the pecl homepage. during the pecl spin-off, the project has also been renamed from "php extension code library" to "php extension community library".

gtk packages

gtk

gtk packages are packages that provide software which uses the technology of the php-gtk project. code in this sub-repository follows pear's coding standards.

poprzednispis treścinastępny
o pearpoczątek rozdziałuinstallation