From: Rouven Czerwinski <r.czerwinski@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] rauc: select busybox features if using busybox tar
Date: Tue, 26 Feb 2019 11:25:58 +0100 [thread overview]
Message-ID: <1551176758.3420.2.camel@pengutronix.de> (raw)
In-Reply-To: <20190226102249.710-1-r.czerwinski@pengutronix.de>
On Tue, 2019-02-26 at 11:22 +0100, Rouven Czerwinski wrote:
> Select BUSYBOX_CONFIG_FEATURE_TAR_AUTODETECT and
> BUSYBOX_FEATURE_SEAMLESS_XZ if BUSYBOX_TAR is enabled. These options
> are
> required according to the documentation avilable at [1].
> While at it convert the space to tab after if for long options.
>
> [1]: https://rauc.readthedocs.io/en/v1.0/integration.html#required-ta
> rget-tools
>
> Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
> ---
> rules/rauc.in | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/rules/rauc.in b/rules/rauc.in
> index 8c94710f9..fc2315b35 100644
> --- a/rules/rauc.in
> +++ b/rules/rauc.in
> @@ -7,11 +7,14 @@ menuconfig RAUC
> select GLIB
> select GLIB_LIBMOUNT
> select HOST_GLIB
> - select BUSYBOX_FEATURE_TAR_LONG_OPTIONS if BUSYBOX_TAR
> + select BUSYBOX_FEATURE_TAR_LONG_OPTIONS if
> BUSYBOX_TAR
> + select BUSYBOX_FEATURE_TAR_AUTODETECT if BUSYBOX_TAR
> + select BUSYBOX_FEATURE_SEAMLESS_XZ if
> BUSYBOX_TAR
> select LIBCURL if
> RAUC_NETWORK
> select JSON_GLIB if RAUC_JSON
> select SQUASHFS_TOOLS if RUNTIME
> select SQUASHFS_TOOLS_UNSQUASHFS if RUNTIME
> +
Huh, how did that whitespace damage sneak in there? Will send a v2.
> help
> Robust Auto-Update Controller. RAUC controls the update
> process on embedded linux systems.
>
- Rouven
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-02-26 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 10:22 Rouven Czerwinski
2019-02-26 10:25 ` Rouven Czerwinski [this message]
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=1551176758.3420.2.camel@pengutronix.de \
--to=r.czerwinski@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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