From patchwork Wed Feb 6 21:49:05 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [v2,4/5] docs/manual: no longer mention the package/customize thing Date: Wed, 06 Feb 2013 11:49:05 -0000 From: Thomas Petazzoni X-Patchwork-Id: 218776 Message-Id: <1360187346-30258-5-git-send-email-thomas.petazzoni@free-electrons.com> To: buildroot@uclibc.org Signed-off-by: Thomas Petazzoni Acked-by: "Yann E. MORIN" Acked-by: Luca Ceresoli Acked-by: "Samuel Martin" Acked-by: "Samuel Martin" --- docs/manual/customize-rootfs.txt | 6 ------ 1 file changed, 6 deletions(-) diff --git a/docs/manual/customize-rootfs.txt b/docs/manual/customize-rootfs.txt index f1d336a..aea622e 100644 --- a/docs/manual/customize-rootfs.txt +++ b/docs/manual/customize-rootfs.txt @@ -50,12 +50,6 @@ there are a few ways to customize the resulting target filesystem. stored - +BASE_DIR+: the base output directory -* A special package, 'customize', stored in +package/customize+ can be - used. You can put all the files that you want to see in the final - target root filesystem in +package/customize/source+, and then - enable this special package in the configuration system. _This - method is marked as deprecated_. - Note also that if you want to perform some specific actions *after* all filesystem images have been created (for example to automatically extract your root filesystem tarball in a location exported by your