From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] customize package: odd copy construction
Date: Thu, 5 Jan 2012 10:27:02 -0600 [thread overview]
Message-ID: <201201051027.05059.minimod@morethan.org> (raw)
In-Reply-To: <20120105163648.3bf64bcd@skate>
On Thu January 5 2012, Thomas Petazzoni wrote:
> Le Thu, 5 Jan 2012 16:23:23 +0100,
> Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :
>
> > The customize uses an odd copy construction that I can't really explain:
> >
> > rm -f $(BUILD_DIR)/series
> > (cd $(CUST_DIR); \
> > /bin/ls -d * > $(BUILD_DIR)/series || \
> > touch $(BUILD_DIR)/series )
> > for f in `cat $(BUILD_DIR)/series`; do \
> > cp -af $(CUST_DIR)/$$f $(TARGET_DIR); \
> > done
> > rm -f $(BUILD_DIR)/series
> >
> > This was changed from:
> > -cp -af $(CUST_DIR)/* $(TARGET_DIR)/
> >
> > in the following commit:
> > http://git.buildroot.org/buildroot/commit/?id=06cc62f9cfbe43e9d31a07667a6af905b5f34a42
> >
> > Why would you create a series file first if you're removing it
> > immediately afterwards?
> > Doesn't the original copy statement do exactly the same?
>
It looks to me as if the intent was in the handling of symbolic links.
ls -d * does not dereference symbolic links.
Mike
> I don't know, but I'm not sure this customize package is good example
> these days. It should probably be removed, or changed to something
> saner that uses the package infrastructure.
>
> Thomas
next prev parent reply other threads:[~2012-01-05 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 15:23 [Buildroot] customize package: odd copy construction Thomas De Schampheleire
2012-01-05 15:36 ` Thomas Petazzoni
2012-01-05 16:27 ` Michael S. Zick [this message]
2012-01-05 17:06 ` Thomas Petazzoni
2012-01-05 17:19 ` Michael S. Zick
2012-01-06 8:29 ` Thomas De Schampheleire
2012-01-11 17:24 ` Peter Korsgaard
[not found] ` <CAAXf6LX5xef3YE0zO0mDZxaFZ3s8NpfPU_jQaDxq0h-XCWOqxQ@mail.gmail.com>
2012-01-11 21:43 ` Peter Korsgaard
2012-01-12 8:17 ` Thomas De Schampheleire
2012-01-12 8:18 ` Peter Korsgaard
2012-01-06 12:47 ` Shawn J. Goff
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=201201051027.05059.minimod@morethan.org \
--to=minimod@morethan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox