From 036c81b1ccab1aa32a9a7847cc75ebe3d9af9976 Mon Sep 17 00:00:00 2001 From: Jordi Boggiano Date: Tue, 21 Aug 2012 16:04:11 +0200 Subject: [PATCH] Fix package name in docs --- doc/05-repositories.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/05-repositories.md b/doc/05-repositories.md index de9f29ffa..2e2672ccd 100644 --- a/doc/05-repositories.md +++ b/doc/05-repositories.md @@ -68,7 +68,7 @@ The only required field is `packages`. The JSON structure is as follows: { "packages": { - "vendor/packageName": { + "vendor/package-name": { "dev-master": { @composer.json }, "1.0.x-dev": { @composer.json }, "0.0.1": { @composer.json }, @@ -161,7 +161,7 @@ project to use the patched version. If the library is on GitHub (this is the case most of the time), you can simply fork it there and push your changes to your fork. After that you update the project's `composer.json`. All you have to do is add your fork as a repository and update the version constraint to -point to your custom branch. For version constraint naming conventions see +point to your custom branch. For version constraint naming conventions see [Libraries](02-libraries.md) for more information. Example assuming you patched monolog to fix a bug in the `bugfix` branch: