Add document for `add_conflict` and `add_conflicts`.

1 files changed, 15 insertions, 0 deletions

diff --git a/doc/mrbgems/README.md b/doc/mrbgems/README.md
index 571c00450..7ae83ef8a 100644
--- a/doc/mrbgems/README.md
+++ b/doc/mrbgems/README.md
@@ -161,6 +161,21 @@ Its format is same as argument of method `MRuby::Build#gem`, expect that it can'
 When a special version of depedency is required,
 use `MRuby::Build#gem` in *build_config.rb* to override default gem.
 
+If you have conflicting GEMs use either or both of the following methods
+* `spec.add_conflict(gem, *requirements)`
+    * The `requirements` argument is same as in `add_dependency` method.
+* `spec.add_conflicts(*conflicting_gems)`
+
+like following code:
+
+	MRuby::Gem::Specification.new 'some-regexp-binding' do |spec|
+	  spec.license = 'BSD'
+	  spec.author = 'John Doe'
+
+	  spec.add_conflict 'mruby-onig-regexp', '> 0.0.0'
+	  spec.add_conflicts 'mruby-hs-regexp', 'mruby-pcre-regexp', 'mruby-regexp-pcre'
+	end
+
 In case your GEM has more complex build requirements you can use
 the following options additionally inside of your GEM specification: