From b79daf43570544f5e790ee3c65a91b0c8148e68d Mon Sep 17 00:00:00 2001 From: Tarjei Huse Date: Mon, 4 Mar 2013 14:17:43 +0100 Subject: [PATCH] Update troubleshooting.md I never thought of looking in the aliases section of the documentation... --- doc/articles/troubleshooting.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index 1282db7b9..a3735972c 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -50,6 +50,24 @@ This is a list of common pitfalls on using Composer, and how to avoid them. Use: `before_script: COMPOSER_ROOT_VERSION=dev-master composer install` to export the variable for the call to composer. +## Need to override package version + +Let say your project depends on package A which in turn depends on a spesific version of +package B (say 0.1) and you need a different version of that package - version 0.11. + +You fix this by renaming version 0.11 as 0.1: + +composer.json: + { + name: "My project", + require: { + "A": "0.2", + "B": "0.11 as 0.1" + } + } + +Also, se [aliases](aliases.md) for more information. + ## Memory limit errors If composer shows memory errors on some commands: