From dd7da3ced1d062b02c74ca0259bbffc10c4772e9 Mon Sep 17 00:00:00 2001 From: Damian Mooyman Date: Mon, 10 Jul 2017 15:09:26 +1200 Subject: [PATCH] Adding note on removal of recipes --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index 058962a..3a6b6c8 100644 --- a/README.md +++ b/README.md @@ -58,6 +58,15 @@ version will be detected, and a safe default chosen. $ composer upgrade-recipe silverstripe/recipe-cms ^1.0@dev ``` +## Removing recipes + +As installation of a recipe inlines all dependencies and passes ownership to the root project, +there is no automatic removal process. To remove a recipe, you should manually remove any +required module that is no longer desired via `composer remove `. + +The `provide` reference to the recipe can also be safely removed, although it has no practical result +other than to disable future calls to `upgrade-recipe` on this recipe. + ## Installing or upgrading recipes without inlining them If desired, the optional inline behaviour of recipes can be omitted. Simply use the composer commands `require` and