From patchwork Sun Feb 9 21:10:44 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: jeffball59@gmail.com X-Patchwork-Id: 318627 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from hemlock.osuosl.org (hemlock.osuosl.org [140.211.166.133]) by ozlabs.org (Postfix) with ESMTP id 471FC2C00B0 for ; Mon, 10 Feb 2014 08:11:57 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by hemlock.osuosl.org (Postfix) with ESMTP id 9350F93BAD; Sun, 9 Feb 2014 21:11:56 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from hemlock.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnXYe0G7kJMA; Sun, 9 Feb 2014 21:11:55 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by hemlock.osuosl.org (Postfix) with ESMTP id 011529398C; Sun, 9 Feb 2014 21:11:55 +0000 (UTC) X-Original-To: buildroot@lists.busybox.net Delivered-To: buildroot@osuosl.org Received: from whitealder.osuosl.org (whitealder.osuosl.org [140.211.166.138]) by ash.osuosl.org (Postfix) with ESMTP id CB0571BFA5C for ; Sun, 9 Feb 2014 21:11:53 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id C75468BA96 for ; Sun, 9 Feb 2014 21:11:53 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YizBGX7XCxcF for ; Sun, 9 Feb 2014 21:11:53 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-qa0-f68.google.com (mail-qa0-f68.google.com [209.85.216.68]) by whitealder.osuosl.org (Postfix) with ESMTPS id 146778BA5A for ; Sun, 9 Feb 2014 21:11:52 +0000 (UTC) Received: by mail-qa0-f68.google.com with SMTP id ii20so2596542qab.7 for ; Sun, 09 Feb 2014 13:11:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=QtfHMOpVzvsZA+soBDxn56yW0of+qfMEywhW8gOMy+0=; b=DfbdiLg3d95ddqC0Mr3mFDk5MyZhTw9+XAMQpkDaQTEqIclrePA2jpw+IM5eueN4gN UOQO/ohFB3I70EqP55/ejVoPfiVdeCz0ztK2Bux9ic32TZKAQJexCiz6J2bHQNl9Kfm2 fdlcIgg0gzWLwx0pu1C0nAO6cmYyri0gAZLq6sRQ7shYku1Q4sOcv+Qu4iLA9gG/PFdF g3wGdUpyDz3lSXJE7sxWmzp48x7bHP5EzD6ZnoI25zRRi+enHrWnTXh3KCt1jyRM7Qig C5dGOOAd9iWpSRBmXtQlhqkFelqfOBK0cfnmUgq8QVj+72NnurmXWadxINW4z3nUXZHW +G1w== X-Received: by 10.229.84.198 with SMTP id k6mr25008058qcl.20.1391980311466; Sun, 09 Feb 2014 13:11:51 -0800 (PST) Received: from localhost.localdomain (108-230-75-62.lightspeed.chtnsc.sbcglobal.net. [108.230.75.62]) by mx.google.com with ESMTPSA id r13sm36255749qan.7.2014.02.09.13.11.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Feb 2014 13:11:51 -0800 (PST) From: jeffball59@gmail.com To: buildroot@busybox.net Date: Sun, 9 Feb 2014 16:10:44 -0500 Message-Id: <1391980244-8855-1-git-send-email-jeffball59@gmail.com> X-Mailer: git-send-email 1.7.10.4 In-Reply-To: References: Subject: [Buildroot] [PATCH 1/1] Modified the documentation on customizing a rootfs to be less ambiguous X-BeenThere: buildroot@busybox.net X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: buildroot-bounces@busybox.net Sender: buildroot-bounces@busybox.net From: Jeff Stewart 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 --- 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 + 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