All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Modified the documentation on customizing a rootfs to be less ambiguous
Date: Mon, 10 Feb 2014 18:16:19 +0100	[thread overview]
Message-ID: <52F90963.4060801@mind.be> (raw)
In-Reply-To: <1391980244-8855-1-git-send-email-jeffball59@gmail.com>

On 02/09/14 22:10, jeffball59 at gmail.com wrote:
> From: Jeff Stewart <jeffball59@gmail.com>
> 
> While reading the documentation I was a little confused over the recommended
> method for customizing the target file system.  After sorting it out in the
> IRC channel, I modified the documentation to be a little less ambiguous.
> 
> Signed-off-by: Jeff Stewart <jeffball59@gmail.com>
> ---
>  docs/manual/customize-rootfs.txt |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/docs/manual/customize-rootfs.txt b/docs/manual/customize-rootfs.txt
> index 2cbae99..c23b1af 100644
> --- a/docs/manual/customize-rootfs.txt
> +++ b/docs/manual/customize-rootfs.txt
> @@ -23,7 +23,7 @@ there are a few ways to customize the resulting target filesystem.
>    over the target filesystem after it has been built.  Set
>    +BR2_ROOTFS_OVERLAY+ to the top of the tree.  +.git+, +.svn+, +.hg+
>    directories, +.empty+ files and files ending with +~+ are excluded.
> -  _Among these first 3 methods, this one should be preferred_.
> +  _Among the customization methods, this one should be preferred_.
>  
>  * In the Buildroot configuration, you can specify the paths to one or
>    more *post-build scripts*. These scripts are called in the given order,
> @@ -56,8 +56,8 @@ there are a few ways to customize the resulting target filesystem.
>    installation. Note that this method is *not recommended*, as it
>    duplicates the entire skeleton, which prevents from taking advantage
>    of the fixes or improvements brought to the default Buildroot
> -  skeleton. The recommended method is to use the _post-build scripts_
> -  mechanism described in the previous item.
> +  skeleton. The _post-build scripts_ mechanism described in the previous

 Actually it's the ROOTFS_OVERLAY that should be recommended.

 Regards,
 Arnout

> +  item is recommend over this mechanism.
>  
>  Note also that you can use the *post-image scripts*
>  if you want to perform some specific actions 'after' all
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

      reply	other threads:[~2014-02-10 17:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-09 21:10 [Buildroot] [PATCH 1/1] Modified the documentation on customizing a rootfs to be less ambiguous jeffball59 at gmail.com
2014-02-10 17:16 ` Arnout Vandecappelle [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=52F90963.4060801@mind.be \
    --to=arnout@mind.be \
    --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.