From: Erik Andersen <andersen@codepoet.org>
To: buildroot@busybox.net
Subject: [Buildroot] Are skel.tar.gz and target_skeleton folder duplicates ?
Date: Tue, 14 Nov 2006 23:56:26 -0700 [thread overview]
Message-ID: <20061115065626.GA7600@codepoet.org> (raw)
In-Reply-To: <30f88efd0611130654w598ff5daj8015e3548e2f7b7d@mail.gmail.com>
On Mon Nov 13, 2006 at 03:54:22PM +0100, Benjamin Delagoutte wrote:
> Eventually I don't really understand why Buildroot makes use of
> two different prebuilt trees. Do someone mind explaining me the
> goals of this weird strategy ?
We used to use CVS as our revision control system. CVS refused
to store and restore empty directories and symlinks. As a result
we ended up using a tarball for these items rather than a simple
directory full of stuff. But using a tarball proved to be a real
pain, since using a tarball to store files which tend to be
modified (such as the stuff under /etc for example) is unwieldly
at best. So I created the current hybrid approach.
Subversion is a much more sane revision control system, so I
think we can probably consolidate things now.
<sound of hacking in the distance>
Fixed. Thanks for bringing this up.
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
next prev parent reply other threads:[~2006-11-15 6:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 14:54 [Buildroot] Are skel.tar.gz and target_skeleton folder duplicates ? Benjamin Delagoutte
2006-11-15 6:56 ` Erik Andersen [this message]
2006-11-15 8:18 ` Benjamin Delagoutte
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=20061115065626.GA7600@codepoet.org \
--to=andersen@codepoet.org \
--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.