From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Joachim Wiberg <troglobit@gmail.com>
Cc: buildroot@buildroot.org, Vadim Kochan <vadim4j@gmail.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/frr: make vtysh group configurable
Date: Mon, 6 Jan 2025 22:11:31 +0100 [thread overview]
Message-ID: <20250106221131.4abdc790@windsurf> (raw)
In-Reply-To: <20250106203459.2875914-1-troglobit@gmail.com>
Hello Joachim,
On Mon, 6 Jan 2025 21:34:59 +0100
Joachim Wiberg <troglobit@gmail.com> wrote:
> Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
I am not a big fan of this, because we frequently use a "sane" default
group in packages, and clearly don't want to make such a "sane" default
configurable in each package. We would normally expect people who need
to customize things to do it in their custom post-build script, but I
admit in this specific case it seems not great, so I don't really have
a good idea.
But my main concern is really: do we want to allow config options to
set the group like this for each and every package?
> # Do not enable -fplugin=frr-format for production, see doc/developer/workflow.rst,
> # it is only intended for FRR's developments
> +FRR_VTYSH_GROUP=$(call qstrip,$(BR2_PACKAGE_FRR_VTYSH_GROUP))
Nitpick: spaces needed around = sign.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-01-06 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 20:34 [Buildroot] [PATCH 1/1] package/frr: make vtysh group configurable Joachim Wiberg
2025-01-06 21:11 ` Thomas Petazzoni via buildroot [this message]
2025-01-06 21:27 ` Joachim Wiberg
2025-02-05 1:28 ` Vincent Jardin
2025-02-05 4:14 ` Joachim Wiberg
2025-02-05 8:48 ` Arnout Vandecappelle via buildroot
2025-02-05 8:51 ` Arnout Vandecappelle via buildroot
2025-02-05 9:00 ` Joachim Wiberg
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=20250106221131.4abdc790@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=troglobit@gmail.com \
--cc=vadim4j@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.