info/php-the-right-way
1
0
Fork 0
mirror of https://github.com/codeguy/php-the-right-way.git synced 2025-08-18 11:31:16 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #94 from Blackshawk/gh-pages

Browse Source 
Additional Info on Differences between Composer & PEAR
This commit is contained in:
Phil Sturgeon
2012-07-12 12:19:58 -07:00
parent 53e7b82553 bd8c8026e6
commit 630b79de09
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
_posts/04-01-01-Dependency-Management.md
View File

@@ -1,3 +1,10 @@
# Dependency Management
There are a ton of PHP libraries, frameworks, and components to choose from. Your project will likely use several of them — these are project dependencies. Until recently, PHP did not have a good way to manage these project dependencies. Even if you managed them manually, you still had to worry about autoloaders. No more.
Currently there are two major package management systems for PHP - Composer and PEAR. Which one is right for you? The answer is both.
* Use **Composer** when managing dependencies for a single project.
* Use **PEAR** when managing dependencies for PHP as a whole on your system.
In general, Composer packages will be available only in the projects that you explicitly specify whereas a PEAR package would be available to all of your PHP projects. While PEAR might sound like the easier approach at first glance, there are advantages to using a project-by-project approach to your dependencies.