From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/rabbitmq-server: bump version to 3.8.2
Date: Sat, 1 Feb 2020 22:59:39 +0100 [thread overview]
Message-ID: <20200201225939.12bcd9e1@windsurf> (raw)
In-Reply-To: <20200129172618.16966-3-frank.vanbever@essensium.com>
On Wed, 29 Jan 2020 18:26:18 +0100
Frank Vanbever <frank.vanbever@essensium.com> wrote:
> diff --git a/package/rabbitmq-server/Config.in b/package/rabbitmq-server/Config.in
> index b3b7639e28..10a7c27d68 100644
> --- a/package/rabbitmq-server/Config.in
> +++ b/package/rabbitmq-server/Config.in
> @@ -1,6 +1,7 @@
> config BR2_PACKAGE_RABBITMQ_SERVER
> bool "rabbitmq-server"
> depends on BR2_PACKAGE_ERLANG
> + select BR2_PACKAGE_HOST_ELIXIR
There is no BR2_PACKAGE_HOST_ELIXIR option created by your PATCH 2/3,
and that's good as we don't need one. But then you shouldn't reference
one from here.
> -comment "rabbitmq-server needs erlang"
> - depends on !BR2_PACKAGE_ERLANG
> +comment "rabbitmq-server needs erlang and elixir"
> + depends on !BR2_PACKAGE_ERLANG || !BR2_PACKAGE_HOST_ELIXIR
This change is also not needed, as BR2_PACKAGE_HOST_ELIXIR doesn't
exist.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-01 21:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 17:26 [Buildroot] [PATCH 1/3] package/erlang: bump to version 22.2 Frank Vanbever
2020-01-29 17:26 ` [Buildroot] [PATCH 2/3] package/elixir: new package Frank Vanbever
2020-02-01 22:02 ` Thomas Petazzoni
2020-01-29 17:26 ` [Buildroot] [PATCH 3/3] package/rabbitmq-server: bump version to 3.8.2 Frank Vanbever
2020-02-01 21:59 ` Thomas Petazzoni [this message]
2020-02-01 21:57 ` [Buildroot] [PATCH 1/3] package/erlang: bump to version 22.2 Thomas Petazzoni
2020-02-04 10:07 ` [Buildroot] [PATCH v2 " Frank Vanbever
2020-02-04 10:07 ` [Buildroot] [PATCH v2 2/3] package/elixir: new package Frank Vanbever
2020-02-05 14:42 ` Thomas Petazzoni
2020-02-04 10:07 ` [Buildroot] [PATCH v2 3/3] package/rabbitmq-server: bump version to 3.8.2 Frank Vanbever
2020-02-05 14:47 ` Thomas Petazzoni
2020-02-13 15:14 ` [Buildroot] [PATCH v3 1/2] package/rabbitmq-server: clean up license list Frank Vanbever
2020-02-13 15:14 ` [Buildroot] [PATCH v3 2/2] package/rabbitmq-server: bump version to 3.8.2 Frank Vanbever
2020-04-12 19:33 ` Thomas Petazzoni
2020-04-12 19:33 ` [Buildroot] [PATCH v3 1/2] package/rabbitmq-server: clean up license list Thomas Petazzoni
2020-02-05 9:37 ` [Buildroot] [PATCH v2 1/3] package/erlang: bump to version 22.2 Thomas Petazzoni
2020-02-05 11:15 ` Frank Vanbever
2020-02-05 14:42 ` Thomas Petazzoni
2020-02-10 13:28 ` Johan Oudinet
2020-02-10 13:30 ` Thomas Petazzoni
2020-02-10 15:20 ` Johan Oudinet
2020-02-10 15:27 ` Johan Oudinet
2020-02-10 15:51 ` Johan Oudinet
2020-02-10 15:57 ` Thomas Petazzoni
2020-02-10 16:07 ` Johan Oudinet
2020-02-10 16:48 ` 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=20200201225939.12bcd9e1@windsurf \
--to=thomas.petazzoni@bootlin.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