PEAR: Difference between revisions

link to SO question
No edit summary
 
Line 12: Line 12:


== PEAR in 2016 ==
== PEAR in 2016 ==
Is PEAR still relevant? In the age of GitHub and [[Composer]], if you listen to chatter on the Internet, it's easy to think that PEAR is a moribund project that is also irrelevant.  But it is actually alive and kicking.  Sadly, I don't think that the trends will reverse. Still, you need to know about PEAR and even [https://stackoverflow.com/questions/20804004/installing-php-pear-packages-via-ansible-with-idempotency how to install PEAR with idempotency in Ansible]<ref>In my tests the 'and' trick for failed_when did not work because the new 2.x module does not have .stdout.  There is only msg</ref>
Is PEAR still relevant? In the age of GitHub and [[Composer]], if you listen to chatter on the Internet, it's easy to think that PEAR is a moribund project that is also irrelevant.  But it is actually alive and kicking.  Sadly, I don't think that the trends will reverse. Still, you need to know about PEAR because there are many cases where a PEAR class is underlying your application or hosting platform. [https://stackoverflow.com/questions/20804004/installing-php-pear-packages-via-ansible-with-idempotency How to install PEAR with idempotency in Ansible]<ref>In my tests the 'and' trick for failed_when did not work because the new 2.x module does not have .stdout.  There is only msg https://github.com/ansible/ansible-modules-extras/blob/devel/packaging/language/pear.py</ref>


[[Category:PHP]]
[[Category:PHP]]