From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] dropbear: use BR2_SYSTEM_DEFAULT_PATH as default PATH
Date: Tue, 18 Dec 2018 20:47:32 +0100 [thread overview]
Message-ID: <20181218194732.GF24194@scaer> (raw)
In-Reply-To: <20181218005116.17435-5-mmayer@broadcom.com>
Markus, All,
On 2018-12-17 16:51 -0800, Markus Mayer spake thusly:
> We use the configuration option BR2_SYSTEM_DEFAULT_PATH to set the
> default PATH in dropbear sessions.
Ditto, string already quoted blah-blah-blah... ;-)
> Signed-off-by: Markus Mayer <mmayer@broadcom.com>
> ---
> package/dropbear/dropbear.mk | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/package/dropbear/dropbear.mk b/package/dropbear/dropbear.mk
> index 7b1468cfb100..7dc5f46bcc81 100644
> --- a/package/dropbear/dropbear.mk
> +++ b/package/dropbear/dropbear.mk
> @@ -81,6 +81,14 @@ define DROPBEAR_DISABLE_STANDALONE
> echo '#define NON_INETD_MODE 0' >> $(@D)/localoptions.h
> endef
>
> +ifneq ($(BR2_SYSTEM_DEFAULT_PATH),"")
> +define DROPBEAR_CUSTOM_PATH
> + echo '#define DEFAULT_PATH $(BR2_SYSTEM_DEFAULT_PATH)' >>$(@D)/localoptions.h
> +endef
Why is it conditional here, and not in the two other patches, then?
In fact I think I missed that in the initial patch: we should ensure
that it can't be empty (unelss there is a good reason to accept a
system-wide empty PATH). Maybe something in system/system.mk:
ifeq ($(BR_BUILDLING)$(BR2_SYSTEM_DEFAULT_PATH)),y"")
$(error BR2_SYSTEM_DEFAULT_PATH can't be empty)
endif
(no need to properly finish the sentence, the $(error) will do it for
you.)
And then we can safely use it as-is, unconditionally, in the three other
locations (profile, openssh, dropbear).
Of course, if we decide that an empty BR2_SYSTEM_DEFAULT_PATH is valid,
then we should also use it as-is in dropbear and openssh, because we
should just abide by the user's decision.
Regards,
Yann E. MORIN.
> +DROPBEAR_POST_EXTRACT_HOOKS += DROPBEAR_CUSTOM_PATH
> +endif
> +
> define DROPBEAR_INSTALL_INIT_SYSTEMD
> $(INSTALL) -D -m 644 package/dropbear/dropbear.service \
> $(TARGET_DIR)/usr/lib/systemd/system/dropbear.service
> --
> 2.17.1
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-12-18 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 0:51 [Buildroot] [PATCH 0/4] Allow customization of system default PATH Markus Mayer
2018-12-18 0:51 ` [Buildroot] [PATCH 1/4] system cfg: introduce option BR2_SYSTEM_DEFAULT_PATH Markus Mayer
2018-12-18 19:27 ` Yann E. MORIN
2018-12-18 21:22 ` Markus Mayer
2018-12-18 0:51 ` [Buildroot] [PATCH 2/4] skeleton: use BR2_SYSTEM_DEFAULT_PATH as default PATH Markus Mayer
2018-12-18 19:32 ` Yann E. MORIN
2018-12-18 19:33 ` Yann E. MORIN
2018-12-18 0:51 ` [Buildroot] [PATCH 3/4] openssh: " Markus Mayer
2018-12-18 19:38 ` Yann E. MORIN
2018-12-18 0:51 ` [Buildroot] [PATCH 4/4] dropbear: " Markus Mayer
2018-12-18 19:47 ` Yann E. MORIN [this message]
[not found] ` <CAGt4E5uXpteKpCCt_XmKG2HONQ3PQQADHjSyjeBKRPhphxhWhQ@mail.gmail.com>
2018-12-18 23:16 ` Markus Mayer
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=20181218194732.GF24194@scaer \
--to=yann.morin.1998@free.fr \
--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