All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12666] Doesn't pick up a custom bash profile
Date: Thu, 19 Mar 2020 06:16:51 +0000	[thread overview]
Message-ID: <bug-12666-163-3vKkeEV4Oh@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12666-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12666

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Changing system/skeleton/ is not recommended. Instead, you should create your
own "root filesystem overlay", and use the option BR2_ROOTFS_OVERLAY to point
to it.

Most likely you did your change to system/skeleton/ *after* a build was done,
and you didn't do a clean rebuild from scratch. In this case, it is expected
that you don't see the changes in your image: the skeleton package has already
been built/installed, so it's not reinstalled.

Using a rootfs overlay is cleaner as you don't change the Buildroot default
skeleton, but also because they are copied into the target filesystem at every
"make" invocation.

See https://buildroot.org/downloads/manual/manual.html#rootfs-custom for more
details, as well as
https://bootlin.com/doc/training/buildroot/buildroot-slides.pdf starting from
slide 79.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2020-03-19  6:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19  1:26 [Buildroot] [Bug 12666] New: Doesn't pick up a custom bash profile bugzilla at busybox.net
2020-03-19  6:16 ` bugzilla at busybox.net [this message]
2020-03-19 17:18 ` [Buildroot] [Bug 12666] " bugzilla at busybox.net

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=bug-12666-163-3vKkeEV4Oh@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 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.