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

Updated wording on Composer / PEAR stuff.

Browse Source
This commit is contained in:
Phil Sturgeon
2015-01-02 11:57:33 -05:00
parent 93c00317c8 779932b272
commit d621ed0e41
3 changed files with 72 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -4,16 +4,14 @@ anchor: dependency_management
# Dependency Management {#dependency_management_title}
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.
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.
That is no longer an issue.
Currently there are two major package management systems for PHP - Composer and PEAR. Which one is right for you? The
answer is both.
Currently there are two major package management systems for PHP - [Composer] and [PEAR]. Composer is
the main package manager to use for PHP, however for a long time PEAR used to fill that role. Knowing what
PEAR is will be a good idea as you may still find references to it, even if you never use it.
* 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.
[Composer]: /#composer_and_packagist
[PEAR]: /#pear