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

add possible work-around / solution

pull/4713/head
Rob Bast 2015-12-17 14:13:37 +01:00
parent 8b12e39509
commit 04fb28a9cb
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/articles/pitfalls.md
View File

@ -9,6 +9,8 @@
The [`repositories`](04-schema.md#repositories) configuration property is defined as [root-only] The [`repositories`](04-schema.md#repositories) configuration property is defined as [root-only]
(04-schema.md#root-package). It is not inherited. You can read more about the reasons behind this in the "[why can't (04-schema.md#root-package). It is not inherited. You can read more about the reasons behind this in the "[why can't
composer load repositories recursively?](articles/why-can't-composer-load-repositories-recursively.md)" article. composer load repositories recursively?](articles/why-can't-composer-load-repositories-recursively.md)" article.
The simplest work-around to this limitation, is moving or duplicating the `repositories` definition to your root
composer.json.
## I have locked a dependency to a specific commit but get unexpected results. ## I have locked a dependency to a specific commit but get unexpected results.
@ -22,3 +24,5 @@ frequently overlooked:
> before the hash. Because of that in some cases it will not be a practical > before the hash. Because of that in some cases it will not be a practical
> workaround, and you should always try to switch to tagged releases as soon > workaround, and you should always try to switch to tagged releases as soon
> as you can. > as you can.
There is no simple work-around to this limitation. It is therefor strongly recommended that you do not use it.