public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Update why-can't-composer-load-repositories-recursively.md

pull/6654/head
andrewryantech 2017-09-05 08:55:37 +10:00 committed by GitHub
parent d9885d5b3b
commit a6d0ecd13f
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/faqs/why-can't-composer-load-repositories-recursively.md
View File

@ -29,7 +29,7 @@ dist/source. There are many many ways this could go wrong.
- Fetch the repositories of root package, then fetch the repositories of the - Fetch the repositories of root package, then fetch the repositories of the
first level dependencies, then fetch the repositories of their dependencies, etc, first level dependencies, then fetch the repositories of their dependencies, etc,
then resolve requirements. This sounds more efficient, but it suffers from the then resolve requirements. This sounds more efficient, but it suffers from the
same problems than the second solution, because loading the repositories of the same problems as the second solution, because loading the repositories of the
dependencies is not as easy as it sounds. You need to load all the repos of all dependencies is not as easy as it sounds. You need to load all the repos of all
the potential matches for a requirement, which again might have conflicting the potential matches for a requirement, which again might have conflicting
package definitions. package definitions.