From 7dfcd2418aacbdb5e123fb23ac735acfdd6c588d Mon Sep 17 00:00:00 2001
From: Sebastian Bergmann <sb@sebastian-bergmann.de>
Date: Mon, 3 Oct 2016 09:44:30 +0200
Subject: [PATCH] Use best practice for adding this library as a dependency
 using Composer

---
 README.md | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 9a40a77..7bbef50 100644
--- a/README.md
+++ b/README.md
@@ -162,10 +162,11 @@ LONG_STRING
 
 ## Installation
 
-To add Exporter as a local, per-project dependency to your project, simply add a dependency on `sebastian/exporter` to your project's `composer.json` file. Here is a minimal example of a `composer.json` file that just defines a dependency on Exporter 1.0:
+You can add this library as a local, per-project dependency to your project using [Composer](https://getcomposer.org/):
+
+    composer require sebastian/exporter
+
+If you only need this library during development, for instance to run your project's test suite, then you should add it as a development-time dependency:
+
+    composer require --dev sebastian/exporter
 
-    {
-        "require": {
-            "sebastian/exporter": "1.0.*"
-        }
-    }