PEAR: Difference between revisions

Content deleted Content added

Inline

Latest revision as of 14:44, 15 February 2024

The PHP Extension and Application Repository, or PEAR, is a repository of PHP software code. Stig S. Bakken founded the PEAR project in 1999 to promote the re-use of code that performs common functions. The project seeks to provide a structured library of code, maintain a system for distributing code and for managing code packages, and promote a standard coding style. Though community-driven, the PEAR project has a PEAR Group which serves as the governing body and takes care of administrative tasks. Each PEAR code package comprises an independent project under the PEAR umbrella. It has its own development team, versioning-control and documentation.

PEAR packages

A PEAR package is distributed as a gzipped tar file. Each archive consists of source code written in PHP, usually in an object-oriented style^{[citation needed]}. Many PEAR packages can readily be used by developers as ordinary third party code via simple include statements in PHP. More elegantly, the PEAR package manager which comes with PHP by default may be used to install PEAR packages so that the extra functionality provided by the package appears as an integrated part of the PHP installation. Unlike the Comprehensive Perl Archive Network (CPAN) archives, which PEAR took as its model^{[citation needed]}, PEAR packages do not have implicit dependencies so that a package's placement in the PEAR package tree does not relate to code dependencies. Rather, PEAR packages must explicitly declare all dependencies on other PEAR packages.

The PEAR base classes contain code for simulating object-oriented destructors and consistent error-handling. Packages exist for many basic PHP functions including authentication, caching, database access, encryption, configuration, HTML, web services and XML.

PEAR means “PHP Extension and Application Repository.” It is a framework and distribution system for reusable PHP components. It extends PHP and gives a higher level of programming for all web developers. PEAR is divided into three different classes that are: PEAR Core Components, PEAR Packages, and PECL Packages. The PEAR Packages include functionality giving for authentication, networking, and file system features and tools for working with HTML and XML templates.

PEAR package manager

The PEAR package manager provides a standardized way to install, uninstall, or upgrade with new PEAR packages or PECL extensions. Before installing a package it can also be instructed to take care of package dependencies so all the extra needed packages are installed too.

The PEAR package manager is run from the command line using the pear command. Usually it is therefore only the server administrator who can alter the installed base of PEAR and PECL extensions. On PHP installations running on Linux, the PEAR package manager is ready for usage by default, but on Windows the PEAR package manager is only available after running a batch file called go-pear.bat.

PEAR2 Pyrus

With Pyrus an attempt was undertaken to redesign and improve PEAR from the ground up for PHP 5.3 or newer.^[1] Pyrus can be used to install packages from PEAR channels. The last release is from March 2011 and its development might have been discontinued due to the popularity of Composer.^[2]

PEAR and Composer

With Composer there is an alternative available for managing packages for a PHP project. Composer also supports the installation of PEAR packages.^[3] Some people ^{[by whom?]} of the PHP community argue for replacing PEAR in favor of composer.^[4] ^[5]

PECL

The PHP Extension Community Library (PECL), (pronounced 'pickle'^[6]) is conceptually very similar to PEAR, and indeed PECL modules are installed with the PEAR Package Manager. PECL contains C extensions for compiling into PHP. As C programs, PECL extensions run more efficiently than PEAR packages. PECL includes modules for XML-parsing, access to additional databases, mail-parsing, embedding Perl or Python in PHP scripts and for compiling PHP scripts. PECL spun off from the PEAR Project in October 2003. Originally it was called the PEAR Extension Code Library, but it now operates independently of PEAR.^[7]

PECL extensions are documented alongside standard extensions within the PHP Manual, so there is no special manual for PECL extensions. Also, several^{[example needed]} extensions began their development cycle in PECL and ended up in core (the distributed PHP source) and in many^{[example needed]} of these cases the PECL versions become unmaintained.

References

^ "PEAR2_Pyrus - PEAR2". Archived from the original on 2017-01-10. Retrieved 2016-12-12.
^ "PHP - What is the difference between PEAR and Composer?".
^ "Repositories - Composer".
^ "The rise of Composer and the fall of PEAR |Articles - Fabien Potencier".
^ "Blast from the Past - Is PEAR still relevant?".
^ "Manual :: What is PEAR?". pear.php.net. Retrieved 2017-03-21.
^ Jansen, Martin (October 15, 2003). "Own infrastructure for PECL". News. PEAR. PEAR Website Team. Archived from the original on 2023-02-28. Retrieved 2023-02-28. PECL, formerly known as PHP Extension Code Library, has been renamed to PHP Extension Community Library.{{cite web}}: CS1 maint: bot: original URL status unknown (link)

External links

[1] "PEAR2_Pyrus - PEAR2". Archived from the original on 2017-01-10. Retrieved 2016-12-12.

[2] "PHP - What is the difference between PEAR and Composer?".

[3] "Repositories - Composer".

[4] "The rise of Composer and the fall of PEAR |Articles - Fabien Potencier".

[5] "Blast from the Past - Is PEAR still relevant?".

[6] "Manual :: What is PEAR?". pear.php.net. Retrieved 2017-03-21.

[pear-news20031015-7] Jansen, Martin (October 15, 2003). "Own infrastructure for PECL". News. PEAR. PEAR Website Team. Archived from the original on 2023-02-28. Retrieved 2023-02-28. PECL, formerly known as PHP Extension Code Library, has been renamed to PHP Extension Community Library.{{cite web}}: CS1 maint: bot: original URL status unknown (link)

[1]

[2]

[3]

[4]

[5]

[6]

[7]

@@ Line 1: / Line 1: @@
+{{Short description|Repository of PHP software code}}
-{{otheruses|Pear (disambiguation)}}
+{{other uses|Pear (disambiguation)}}
 The '''PHP Extension and Application Repository''', or '''PEAR''', is a repository of [[PHP]] software code.  [[Stig Bakken|Stig S. Bakken]] founded the PEAR project in 1999 to promote the [[code reuse|re-use]] of code that performs common functions. The project seeks to provide a structured [[library (computer science)|library]] of code, maintain a system for distributing code and for managing [[code package]]s, and promote a standard coding style. Though community-driven, the PEAR project has a PEAR Group which serves as the governing body and takes care of administrative tasks. Each PEAR code package comprises an independent project under the PEAR umbrella.  It has its own development team, versioning-control and documentation.
 ==PEAR packages==
-A '''PEAR package''' is distributed as a [[gzip]]ped [[tar file]]. Each archive consists of source code written in [[PHP]], {{citation needed span|text=usually in an [[object-oriented]] style|date=July 2015}}. Many PEAR packages can readily be used by developers as ordinary third party code via simple include statements in PHP. More elegantly, the '''PEAR [[package manager]]''' which comes with PHP by default may be used to install PEAR packages so that the extra functionality provided by the package appears as an integrated part of the PHP installation. Unlike the [[CPAN|Comprehensive Perl Archive Network]] (CPAN) archives, {{citation needed span|text=which PEAR took as its model|date=July 2015}}, PEAR packages do not have implicit dependencies so that a package's placement in the PEAR package tree does not relate to code dependencies.  Rather, PEAR packages must explicitly declare all dependencies on other PEAR packages.
+A PEAR package is distributed as a [[gzip]]ped [[tar file]]. Each archive consists of source code written in [[PHP]], {{citation needed span|text=usually in an [[object-oriented]] style|date=July 2015}}. Many PEAR packages can readily be used by developers as ordinary third party code via simple include statements in PHP. More elegantly, the PEAR [[package manager]] which comes with PHP by default may be used to install PEAR packages so that the extra functionality provided by the package appears as an integrated part of the PHP installation. Unlike the [[CPAN|Comprehensive Perl Archive Network]] (CPAN) archives, {{citation needed span|text=which PEAR took as its model|date=July 2015}}, PEAR packages do not have implicit dependencies so that a package's placement in the PEAR package tree does not relate to code dependencies.  Rather, PEAR packages must explicitly declare all dependencies on other PEAR packages.
 The PEAR base [[class (computer science)|class]]es contain code for simulating [[Object-oriented programming|object-oriented]] [[destructor (computer science)|destructor]]s and consistent error-handling.  Packages exist for many basic PHP functions including [[authentication]], [[web cache|caching]], database access, [[encryption]], configuration, [[HTML]], [[web services]] and [[XML]].
+PEAR means “PHP Extension and Application Repository.” It is a framework and distribution system for reusable PHP components. It extends PHP and gives a higher level of programming for all web developers. PEAR is divided into three different classes that are: PEAR Core Components, PEAR Packages, and PECL Packages. The PEAR Packages include functionality giving for authentication, networking, and file system features and tools for working with HTML and XML templates.
 == PEAR package manager ==
 The PEAR package manager provides a standardized way to install, uninstall, or upgrade with new PEAR packages or PECL extensions. Before installing a package it can also be instructed to take care of package dependencies so all the extra needed packages are installed too.
-The PEAR package manager is run from the command line using the <code>pear</code> command. Usually it is therefore only the server administrator who can alter the installed base of PEAR and PECL extensions. On PHP installations running on Linux, the PEAR package manager is ready for usage by default, but on Windows the PEAR package manager is only available after running a batch file called <code>go-pear.bat</code>.
+The PEAR package manager is run from the command line using the <code>pear</code> command. Usually it is therefore only the server administrator who can alter the installed base of PEAR and PECL extensions. On PHP installations running on Linux, the PEAR package manager is ready for usage by default, but on Windows the PEAR package manager is only available after running a [[batch file]] called <code>go-pear.bat</code>.
+== PEAR2 Pyrus ==
+With Pyrus an attempt was undertaken to redesign and improve PEAR from the ground up for PHP 5.3 or newer.<ref>{{Cite web |url=https://pear2.php.net/PEAR2_Pyrus |title=PEAR2_Pyrus - PEAR2 |access-date=2016-12-12 |archive-url=https://web.archive.org/web/20170110094110/http://pear2.php.net/PEAR2_Pyrus |archive-date=2017-01-10 |url-status=dead }}</ref>
+Pyrus can be used to install packages from PEAR channels.
+The last release is from March 2011 and its development might have been discontinued due to the popularity of Composer.<ref>{{Cite web|url=https://stackoverflow.com/questions/34199824/what-is-the-difference-between-pear-and-composer|title=PHP - What is the difference between PEAR and Composer?}}</ref>
+== PEAR and Composer ==
+With [[Composer (software)|Composer]] there is an alternative available for managing packages for a PHP project.
+Composer also supports the installation of PEAR packages.<ref>{{Cite web|url=https://getcomposer.org/doc/05-repositories.md#pear|title=Repositories - Composer}}</ref>
+Some people  {{By whom|date=September 2020}} of the PHP community argue for replacing PEAR in favor of composer.<ref>{{Cite web|url=http://fabien.potencier.org/the-rise-of-composer-and-the-fall-of-pear.html|title = The rise of Composer and the fall of PEAR &#124;Articles - Fabien Potencier}}</ref>
+<ref>{{Cite web|url=https://thephp.cc/articles/blast-from-the-past|title = Blast from the Past - Is PEAR still relevant?}}</ref>
 ==PECL==
-'''PECL''' (PHP Extension Community Library, {{citation needed span|text=pronounced 'pickle'|date=July 2015}}) is conceptually very similar to PEAR, and indeed PECL modules are installed with the PEAR Package Manager. PECL contains [[C (programming language)|C]] extensions for compiling into PHP. As C programs, PECL extensions run more efficiently than PEAR packages. PECL includes modules for XML-parsing, access to additional databases, mail-parsing, embedding [[Perl]] or [[Python (programming language)|Python]] in PHP scripts and for compiling PHP scripts.  PECL spun off from the PEAR Project in October 2003. {{citation needed span|text=Originally it was called the PEAR Extension Code Library, but it now operates independently of PEAR.|date=July 2015}}
+The PHP Extension Community Library (PECL), (pronounced 'pickle'<ref>{{Cite web|url=https://pear.php.net/manual/en/about.pear.php|title=Manual :: What is PEAR?|website=pear.php.net|access-date=2017-03-21}}</ref>) is conceptually very similar to PEAR, and indeed PECL modules are installed with the PEAR Package Manager. PECL contains [[C (programming language)|C]] extensions for compiling into PHP. As C programs, PECL extensions run more efficiently than PEAR packages. PECL includes modules for XML-parsing, access to additional databases, mail-parsing, embedding [[Perl]] or [[Python (programming language)|Python]] in PHP scripts and for compiling PHP scripts.  PECL spun off from the PEAR Project in October 2003. Originally it was called the PEAR Extension Code Library, but it now operates independently of PEAR.<ref name="pear-news20031015">{{cite web |url=https://pear.php.net/news/pecl-split.php |title=Own infrastructure for PECL |last=Jansen |first=Martin |date=2003-10-15 |df=mdy |department=News |website=[[PEAR]] |publisher=PEAR Website Team |access-date=2023-02-28 |quote=PECL, formerly known as PHP Extension Code Library, has been renamed to PHP Extension Community Library. |url-status=bot: unknown |archive-url=https://web.archive.org/web/20230228205534/https://pear.php.net/news/pecl-split.php |archive-date=2023-02-28 }}</ref>
 PECL extensions are documented alongside standard extensions within the PHP Manual, so there is no special manual for PECL extensions. Also, several{{examples|date=July 2015}} extensions began their development cycle in PECL and ended up in core (the distributed PHP source) and in many{{examples|date=July 2015}} of these cases the PECL versions become unmaintained.
+==See also==
+*[[Composer (software)]]
+==References==
+{{Reflist}}
 == External links ==
@@ Line 23: / Line 43: @@
 {{PHP}}
 {{Application frameworks}}
+{{Package management systems}}
 [[Category:PHP software]]
-[[Category:Web application frameworks]]
+[[Category:Web frameworks]]
 [[Category:Archive networks]]
 [[Category:Free package management systems]]

v t e PHP
People	Andi Gutmans Rasmus Lerdorf Zeev Suraski
Resources	Accelerator (List) Composer Editors Libraries PEAR
Implementations	HHVM HPHPc Parrot PeachPie Phalanger Quercus Zend Engine
Web frameworks	CakePHP CodeIgniter Drupal eZ Publish Fat-Free Flow FuelPHP Grav Gyroscope Horde Joomla! Laminas Laravel li₃ Midgard MODX Nette Phalcon PHP-Fusion PHP-Nuke Pop PHP PRADO ProcessWire Qcodo Silverstripe Symfony TYPO3 WordPress XOOPS Yii
Testing	Behat PHPUnit
ORMs	Doctrine
IDEs	Aptana Codelobster Eclipse PDT NetBeans PHPEdit PhpStorm Zend Studio
Widget toolkit	PHP-GTK wxPHP
Category Commons

v t e Web frameworks
Comparison
.NET	ASP.NET Core AJAX Dynamic Data MVC Razor Web Forms Blazor DNN BFC MonoRail Umbraco WebSharper
C++	CppCMS Drogon Wt
ColdFusion	ColdBox Platform
Common Lisp	CL-HTTP
Haskell	Servant Snap Yesod
Java	AppFuse Grails GWT ICEfaces JHipster JWt Mojarra Play Remote Application Platform Seam Sling Spring Stripes Struts Tapestry Vaadin Vert.x Wicket WaveMaker ZK
JavaScript	Angular/AngularJS Backbone.js Closure Dojo Toolkit Ember.js Express.js Ext JS Fastify htmx jQuery Knockout.js Meteor MooTools NestJS Next.js Nuxt.js Node.js OpenUI5 Prototype React Remix Sencha Touch SproutCore Svelte Vue.js
Perl	Catalyst Dancer Maypole Mojolicious WebGUI
PHP	CakePHP CodeIgniter Drupal eZ Publish Fat-Free Flow FuelPHP Grav Gyroscope Horde Joomla! Laminas Laravel li₃ Midgard MODX Phalcon PHP-Fusion PHP-Nuke Pop PHP PRADO ProcessWire Qcodo Silverstripe Symfony TYPO3 WordPress XOOPS Yii
Python	BlueBream CherryPy CubicWeb Django FastAPI Flask Grok Nevow Pyjs Pylons Pyramid Quixote TACTIC Tornado TurboGears web2py Zope 2 more...
Ruby	Merb Padrino Ruby on Rails Sinatra
Rust	Rocket
Scala	Lift Play Scalatra
Smalltalk	AIDA/Web Seaside
Other languages	Application Express (PL/SQL) Grails (Groovy) OpenACS (Tcl) Phoenix (Elixir) Shiny (web framework) (R) SproutCore (JavaScript-Ruby) Yaws (Erlang)