From: Markus Mayer <mmayer@broadcom.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] Allow customization of system default PATH
Date: Mon, 17 Dec 2018 16:51:12 -0800 [thread overview]
Message-ID: <20181218005116.17435-1-mmayer@broadcom.com> (raw)
Following an earlier patch submission[1] and a subsequent discussion[2],
here is the resulting patch series to handle the default PATH on the system
in a more generic manner.
What do you think of this initial round of patches?
Thanks,
-Markus
[1] http://lists.busybox.net/pipermail/buildroot/2018-March/215466.html
[2] http://lists.busybox.net/pipermail/buildroot/2018-December/238879.html
Markus Mayer (4):
system cfg: introduce option BR2_SYSTEM_DEFAULT_PATH
skeleton: use BR2_SYSTEM_DEFAULT_PATH as default PATH
openssh: use BR2_SYSTEM_DEFAULT_PATH as default PATH
dropbear: use BR2_SYSTEM_DEFAULT_PATH as default PATH
package/dropbear/dropbear.mk | 8 ++++++++
package/openssh/openssh.mk | 1 +
package/skeleton-init-common/skeleton-init-common.mk | 3 +++
system/Config.in | 10 ++++++++++
system/skeleton/etc/profile | 1 +
5 files changed, 23 insertions(+)
--
2.17.1
next reply other threads:[~2018-12-18 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 0:51 Markus Mayer [this message]
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
[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=20181218005116.17435-1-mmayer@broadcom.com \
--to=mmayer@broadcom.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