From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] bash: add default bash settings
Date: Sun, 20 Dec 2015 15:27:39 +0100 [thread overview]
Message-ID: <20151220152739.2236b56e@free-electrons.com> (raw)
In-Reply-To: <1444674610-8022-1-git-send-email-dvanarnem@cmlab.biz>
David,
On Mon, 12 Oct 2015 12:30:10 -0600, David Van Arnem wrote:
> Settings that were bash-specific were previously removed from
> system/skeleton/etc/profile. This measn that users using bash no longer
> get the "normal" bash prompt with [user at host dir]#/$, and only get #/$.
> This commit adds back the bash-specific settings, but adds them to the
> bash package so they are only used when bash is installed on the target
> system.
>
> bash_profile.sh contains the variables, aliases, and color profile that
> were previously in system/skeleton/etc/profile. The changes to bash.mk
> use a post-install hook to install bash_profile.sh to the target
> filesystem, where it will later be sourced by /etc/profile when a bash
> shell is started.
> ---
> Changes v1 -> v2
> - only export PS1 variable for bash_profile.sh
>
> Signed-off-by: David Van Arnem <dvanarnem@cmlab.biz>
Having this or that shell prompt is really a user-specific
choice/configuration. You can already customize that very easily by
keeping this bash_profile.sh file in your rootfs overlay.
Therefore, I don't think it's really useful to have such customization
by default in Buildroot, and I prefer to not take this patch.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-20 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 18:30 [Buildroot] [PATCH v2] bash: add default bash settings David Van Arnem
2015-12-20 14:27 ` Thomas Petazzoni [this message]
2015-12-20 15:43 ` Yann E. MORIN
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=20151220152739.2236b56e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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