Browse Source

docs/manual: document <pkg>_KEEP_DEPENDENCIES in rebar-package infra

Signed-off-by: Johan Oudinet <johan.oudinet@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Johan Oudinet 5 years ago
parent
commit
e16310c15a
1 changed files with 6 additions and 0 deletions
  1. 6 0
      docs/manual/adding-packages-rebar.txt

+ 6 - 0
docs/manual/adding-packages-rebar.txt

@@ -86,6 +86,12 @@ If the package bundles a _rebar_ utility, but can use the generic
 * +ERLANG_FOOBAR_REBAR_ENV+, to specify additional environment
 * +ERLANG_FOOBAR_REBAR_ENV+, to specify additional environment
   variables to pass to the _rebar_ utility.
   variables to pass to the _rebar_ utility.
 
 
+* +ERLANG_FOOBAR_KEEP_DEPENDENCIES+, to keep the dependencies
+  described in the rebar.config file. Valid values are +YES+ or +NO+
+  (the default). Unless this variable is set to +YES+, the _rebar_
+  infrastructure removes such dependencies in a post-patch hook to
+  ensure rebar does not download nor compile them.
+
 With the rebar infrastructure, all the steps required to build
 With the rebar infrastructure, all the steps required to build
 and install the packages are already defined, and they generally work
 and install the packages are already defined, and they generally work
 well for most rebar-based packages. However, when required, it is
 well for most rebar-based packages. However, when required, it is