Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Customize package not copy .svn .git etc?
Date: Tue, 7 Feb 2012 20:53:00 +0100	[thread overview]
Message-ID: <201202072053.00460.arnout@mind.be> (raw)
In-Reply-To: <jgrm1h$3h3$1@dough.gmane.org>

On Tuesday 07 February 2012 18:12:17 Grant Edwards wrote:
> The other obvious choice would be to use tar:
> 
> $(BUILD_DIR)/.customize:
>         tar -c -f - -C $(CUST_DIR) --exclude-vcs --exclude-backup . | tar -x -f - -C $(TARGET_DIR)
>         touch $@
> 
> I'd be happy to submit a patch containing the latter if everybody
> agrees that they don't want vcs files, backup files, and lockfiles
> copied.  It is specific to gnu tar -- I assume that's not a problem?

 The tar way is indeed a good idea.  And if you use $(TAR) instead of
plain tar, it's guaranteed to be gnu tar.

 As Luca mentioned, customize will be deprecated in favour of the 
rootfs-additions approach.  We'll add this to the target/generic/Config.in
and target-finalize.  If you'd like to prepare a patch for that, you're
more than welcome!

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
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:[~2012-02-07 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07 16:45 [Buildroot] Customize package not copy .svn .git etc? Grant Edwards
2012-02-07 17:08 ` Luca Ceresoli
2012-02-07 17:54   ` Grant Edwards
2012-02-07 17:12 ` Grant Edwards
2012-02-07 19:53   ` 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=201202072053.00460.arnout@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox