Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/libyang: enable LYD_PRIV option for frr package
Date: Tue, 25 Feb 2020 09:06:38 +0100	[thread overview]
Message-ID: <20200225090638.5981818e@windsurf> (raw)
In-Reply-To: <20200225025850.17209-2-vadim4j@gmail.com>

On Tue, 25 Feb 2020 04:58:49 +0200
Vadim Kochan <vadim4j@gmail.com> wrote:

> This option is required by frr package, so enable it only if frr is
> selected.
> 
> Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
> ---
>  package/libyang/libyang.mk | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/package/libyang/libyang.mk b/package/libyang/libyang.mk
> index 648ffeb6a3..9d7f5df696 100644
> --- a/package/libyang/libyang.mk
> +++ b/package/libyang/libyang.mk
> @@ -17,6 +17,10 @@ LIBYANG_CONF_OPTS = \
>  	-DENABLE_VALGRIND_TESTS=OFF \
>  	-DGEN_PYTHON_BINDINGS=OFF
>  
> +ifeq ($(BR2_PACKAGE_FRR),y)

We normally don't look at which reverse dependencies are enabled to
enable features in a dependent package. We do the opposite: look at
which of our dependencies are available to enable features.

What is the size increase of enabling this option? If it is
significant, we want to introduce a BR2_PACKAGE_LIBYANG_LYD_PRIV
sub-option, and select it from the frr package.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-02-25  8:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-25  2:58 [Buildroot] [PATCH v2 0/2] add frr package Vadim Kochan
2020-02-25  2:58 ` [Buildroot] [PATCH v2 1/2] package/libyang: enable LYD_PRIV option for " Vadim Kochan
2020-02-25  8:06   ` Thomas Petazzoni [this message]
2020-02-25  2:58 ` [Buildroot] [PATCH v2 2/2] package/frr: new package Vadim Kochan
2020-02-25  8:25   ` Heiko Thiery
2020-02-25 11:47     ` Vadim Kochan
2020-02-25 10:13   ` Heiko Thiery
2020-02-25 11:46     ` Vadim Kochan
2020-02-25 12:39       ` Heiko Thiery
2020-02-25 15:37         ` Vadim Kochan
2020-02-25 15:38           ` Vadim Kochan

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=20200225090638.5981818e@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