Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] makedevs and symbolic links
Date: Thu, 07 Feb 2013 18:14:28 +0100	[thread overview]
Message-ID: <5113E0F4.4070404@mind.be> (raw)
In-Reply-To: <CAJkQPO=A+_7t-dbSP8VutAsen+MvG9J44qx3D6uxKt7C2mBQUg@mail.gmail.com>

On 07/02/13 11:14, Aras Vaichas wrote:
> My current employer wants me to put my Buildroot configuration into their
> version control system (MKS). So I am looking at ways that I can avoid
> using empty directories and symbolic links to make it diff and MKS
> friendly. I guess there's no getting around using multiple files and
> scripts to achieve this.

  Empty directories, I forgot about that!

  Patch coming up. It excludes the .empty files, so that you can create 
an empty directory in your VCS by populating it with a '.empty' file. We 
use the same trick in the skeleton (git doesn't support empty directories 
either).

  For symlinks, I don't see a reason to add a workaround in buildroot. A 
VCS that doesn't have symlinks is broken. I have a customer who uses CVS, 
and their workaround is to put the overlay in a tar file and extract it 
before building.


  Regards,
  Arnout

-- 
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

  parent reply	other threads:[~2013-02-07 17:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06 16:17 [Buildroot] makedevs and symbolic links Aras Vaichas
2013-02-06 16:26 ` Thomas Petazzoni
2013-02-06 16:50   ` Aras Vaichas
2013-02-06 16:57     ` Thomas Petazzoni
2013-02-07 10:14       ` Aras Vaichas
2013-02-07 10:43         ` Thomas Petazzoni
2013-02-07 17:14         ` Arnout Vandecappelle [this message]
2013-02-07 21:58         ` [Buildroot] [PATCH] rootfs-overlay: also exclude .empty files Arnout Vandecappelle
2013-02-08  5:15           ` Samuel Martin
2013-02-08 21:18           ` Peter Korsgaard

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=5113E0F4.4070404@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