Changes

It's a glue framework, meaning it contains independent packages that can be chosen and "glued" together in your application to meet your requirements. Since PEAR dates back to the origins of [[PHP]], it is oftentimes an underlying requirement for basic PHP functionality which other developers build upon. For a hypothetical example, you could have a [[Drupal ]] module developer use an underlying PEAR package for critical functionality at the system level, while the module proper deals with application integration and extension of Drupal capabilities.

* Brion Vibber (CTO of MediaWiki Foundation) is now a PEAR developer http://leuksman.com/log/* Jean-Lou Dupont http://blog.jldupont.com/2008/03/pear-web-installer.html (his mediawiki extensions are at http://code.google.com/p/mediawiki/ - although he is not actively developing for MediaWiki)

<source lang="bash">= PEAR in 2016 ==# update your pear installationsudo pear upgrade pear# add Jean-lou DupontIs PEAR still relevant? In the age of GitHub and [[Composer]], if you listen to chatter on the Internet, it's channelsudo pear channel-discover mediawikieasy to think that PEAR is a moribund project that is also irrelevant.googlecode But it is actually alive and kicking.com/svn# install Sadly, I don't think that the web front-endsudo pear install PEAR_Frontend_WEB# which fails because it's 'beta' trends will reverse. Still, you need to know about PEAR and our package preference is set even how to 'stable'# therefore install use it specificallysudo pear install channel://pearwith idempotency in [[Ansible]].php.net/PEAR_Frontend_WEB-0.7.4</source>