From: Johan Oudinet <johan.oudinet@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] docs/manual: Document ERLANG_FOOBAR_KEEP_DEPENDENCIES in rebar infra
Date: Wed, 5 Dec 2018 17:06:18 +0100 [thread overview]
Message-ID: <20181205160618.6884-3-johan.oudinet@gmail.com> (raw)
In-Reply-To: <20181205160618.6884-1-johan.oudinet@gmail.com>
Signed-off-by: Johan Oudinet <johan.oudinet@gmail.com>
---
docs/manual/adding-packages-rebar.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/manual/adding-packages-rebar.txt b/docs/manual/adding-packages-rebar.txt
index be9ede0113..d78b3171d8 100644
--- a/docs/manual/adding-packages-rebar.txt
+++ b/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
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
and install the packages are already defined, and they generally work
well for most rebar-based packages. However, when required, it is
--
2.17.1
next prev parent reply other threads:[~2018-12-05 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 16:06 [Buildroot] [PATCH 1/3] package/pkg-rebar.mk: Fix remove-rebar-config-dependencies Johan Oudinet
2018-12-05 16:06 ` [Buildroot] [PATCH 2/3] package/pkg-rebar.mk: Change semantic of <PKG>_KEEP_DEPENDENCIES Johan Oudinet
2018-12-05 16:06 ` Johan Oudinet [this message]
2018-12-09 16:29 ` [Buildroot] [PATCH 1/3] package/pkg-rebar.mk: Fix remove-rebar-config-dependencies Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181205160618.6884-3-johan.oudinet@gmail.com \
--to=johan.oudinet@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox