From a6d0ecd13f4974bd4c1c5cb48a243347d1022986 Mon Sep 17 00:00:00 2001 From: andrewryantech Date: Tue, 5 Sep 2017 08:55:37 +1000 Subject: [PATCH] Update why-can't-composer-load-repositories-recursively.md --- doc/faqs/why-can't-composer-load-repositories-recursively.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/faqs/why-can't-composer-load-repositories-recursively.md b/doc/faqs/why-can't-composer-load-repositories-recursively.md index 56127f7dd..efcd00772 100644 --- a/doc/faqs/why-can't-composer-load-repositories-recursively.md +++ b/doc/faqs/why-can't-composer-load-repositories-recursively.md @@ -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 first level dependencies, then fetch the repositories of their dependencies, etc, 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 the potential matches for a requirement, which again might have conflicting package definitions.