Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Oudinet <johan.oudinet@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: Document ERLANG_FOOBAR_KEEP_DEPENDENCIES in rebar infra
Date: Mon,  3 Dec 2018 12:19:47 +0100	[thread overview]
Message-ID: <20181203111947.32627-1-johan.oudinet@gmail.com> (raw)
In-Reply-To: <20181126110807.31431-2-johan.oudinet@gmail.com>

Signed-off-by: Johan Oudinet <johan.oudinet@gmail.com>
---
 docs/manual/adding-packages-rebar.txt | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/docs/manual/adding-packages-rebar.txt b/docs/manual/adding-packages-rebar.txt
index be9ede0113..b2028b1c5b 100644
--- a/docs/manual/adding-packages-rebar.txt
+++ b/docs/manual/adding-packages-rebar.txt
@@ -86,6 +86,13 @@ 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. By default, the _rebar_
+  infrastructure removes such dependencies as a post-patch hook to
+  ensure rebar does not download or compile them. Only set this
+  variable to a non-empty value if the _rebar_ infrastructure must not
+  modify the rebar.config file included in the package.
+
 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

  parent reply	other threads:[~2018-12-03 11:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 11:07 [Buildroot] [PATCH 00/15] Bump ejabberd to version 18.09 Johan Oudinet
2018-11-26 11:07 ` [Buildroot] [PATCH 01/15] package/pkg-rebar.mk: Remove dependencies from rebar.config Johan Oudinet
2018-11-28 21:28   ` Thomas Petazzoni
2018-12-03 13:14     ` Johan Oudinet
2018-12-03 11:19   ` Johan Oudinet [this message]
2018-12-03 21:14     ` [Buildroot] [PATCH] docs/manual: Document ERLANG_FOOBAR_KEEP_DEPENDENCIES in rebar infra Thomas Petazzoni
2018-12-05 16:17       ` Johan Oudinet
2018-11-26 11:07 ` [Buildroot] [PATCH 02/15] erlang-p1-utils: Bump to version 1.0.13 Johan Oudinet
2018-11-28 21:39   ` Thomas Petazzoni
2018-11-26 11:07 ` [Buildroot] [PATCH 03/15] erlang-p1-cache-tab: Bump to version 1.0.16 Johan Oudinet
2018-11-26 11:07 ` [Buildroot] [PATCH 04/15] erlang-p1-tls: Bump to version 1.0.25 Johan Oudinet
2018-11-26 11:07 ` [Buildroot] [PATCH 05/15] erlang-p1-stringprep: Bump to version 1.0.14 Johan Oudinet
2018-11-26 11:07 ` [Buildroot] [PATCH 06/15] erlang-p1-xml: Bump to version 1.1.34 Johan Oudinet
2018-11-26 11:07 ` [Buildroot] [PATCH 07/15] erlang-p1-zlib: Bump to version 1.0.4 Johan Oudinet
2018-11-26 11:08 ` [Buildroot] [PATCH 08/15] erlang-p1-xmpp: Bump to version 1.2.5 Johan Oudinet
2018-11-26 11:08 ` [Buildroot] [PATCH 09/15] erlang-p1-yaml: Bump to version 1.0.17 Johan Oudinet
2018-11-26 11:08 ` [Buildroot] [PATCH 10/15] erlang-p1-oauth2: Bump to version 0.6.3 Johan Oudinet
2018-11-26 11:08 ` [Buildroot] [PATCH 11/15] erlang-p1-stun: Bump to version 1.0.25 Johan Oudinet
2018-11-26 11:14   ` Johan Oudinet
2018-11-26 13:41   ` [Buildroot] [PATCH v2 " Johan Oudinet
2018-11-26 11:08 ` [Buildroot] [PATCH 12/15] erlang-p1-sip: Bump to version 1.0.26 Johan Oudinet
2018-11-26 11:08 ` [Buildroot] [PATCH 13/15] erlang-p1-iconv: Bump to version 1.0.10 Johan Oudinet
2018-11-26 11:08 ` [Buildroot] [PATCH 14/15] erlang-p1-eimp: New package Johan Oudinet
2018-11-28 21:40   ` Thomas Petazzoni
2018-11-26 11:08 ` [Buildroot] [PATCH 15/15] ejabberd: Bump to version 18.09 Johan Oudinet
2018-11-28 21:43   ` Thomas Petazzoni
2018-12-03 14:00     ` Johan Oudinet
     [not found]       ` <20181203140919.eep447v4yoykd5dr@localhost>
2018-12-03 14:40         ` Johan Oudinet

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=20181203111947.32627-1-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