Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Customize package not copy .svn .git etc?
Date: Tue, 07 Feb 2012 18:08:43 +0100	[thread overview]
Message-ID: <4F315A9B.1000207@lucaceresoli.net> (raw)
In-Reply-To: <jgrkfd$m8n$1@dough.gmane.org>

Hi Grant,

Grant Edwards wrote:
> Do other users of the customize package not use svn, git, CVS, etc?

During the Buildroot Developers Day last Friday we agreed that the
customize package is not well-written and not satisfactory, thus it will
be deprecated in 2012.02 and removed in a following release.

A much better method to obtain the same result is to put your board
specific files in board/<company>/<project>/rootfs-additions/, and write
a command in the post-build script to copy these files onto the target
root filesystem.

For more details, see http://free-electrons.com/blog/elce-2011-videos/,
search for "Using Buildroot For a Real Project". There's a video of
Thomas Petazzoni with many best practices for using Buildroot.
My above suggestion comes from slide 24 of his presentation. Thanks
Thomas.

Ah, actually this won't solve your problem with some version control
systems such as Subversion < 1.7 or CVS which create hidden directories
for their metadata.
To solve this problem you should, in my personal order of preference:
- use git, which creates only one hidden dir in the project root, or
- upgrade to Subversion >= 1.7, which created only one dir as git
   does, or
- write your post-build script so that it bypasses .svn and CVS dirs,
   for example using the find command.

Luca

  reply	other threads:[~2012-02-07 17:08 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 [this message]
2012-02-07 17:54   ` Grant Edwards
2012-02-07 17:12 ` Grant Edwards
2012-02-07 19:53   ` Arnout Vandecappelle

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=4F315A9B.1000207@lucaceresoli.net \
    --to=luca@lucaceresoli.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox