From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] makedevs and symbolic links
Date: Thu, 7 Feb 2013 11:43:44 +0100 [thread overview]
Message-ID: <20130207114344.6dfe478e@skate> (raw)
In-Reply-To: <CAJkQPO=A+_7t-dbSP8VutAsen+MvG9J44qx3D6uxKt7C2mBQUg@mail.gmail.com>
Dear Aras Vaichas,
On Thu, 7 Feb 2013 10:14:18 +0000, Aras Vaichas wrote:
> Aaah, I don't have that version of Buildroot. I'm using 2012.11. I can see
> from the mailing lists now that patches were added for the "rootfs-overlay".
This new "rootfs-overlay" thing is really just a little sugar. You can
already do this "rootfs-overlay" by copying
board/<company>/<project>/rootfs-overlay/* to $(TARGET_DIR) in your
custom post-build script. I've been doing that for 2+ years.
> I might have to leave that until it's in the stable release. I'm currently
> documenting how to use Buildroot for my employer (a company with almost
> zero Linux knowledge) on their hardware, so I'd rather stick to official
> release versions for now. I can update my documentation later.
>
> 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.
>
> Crazy idea: If only patch/diff handled empty directories, symlinks,
> devices, permissions and ownerships. Then it could be done entirely in a
> single file that would be 100% friendly in all cases on all operating
> systems.
It is not possible: you can't create device files without being root,
and you can't change ownership without being root.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-07 10:43 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 [this message]
2013-02-07 17:14 ` Arnout Vandecappelle
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=20130207114344.6dfe478e@skate \
--to=thomas.petazzoni@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.