From: Phil Blundell <philb@gnu.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: oe-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] staging: Avoid staging the same binaries again and again
Date: Mon, 24 Sep 2012 10:59:57 +0100 [thread overview]
Message-ID: <1348480798.31293.26.camel@phil-desktop> (raw)
In-Reply-To: <1348480442.4486.3.camel@ted>
On Mon, 2012-09-24 at 10:54 +0100, Richard Purdie wrote:
> I'm torn whether its better to be simple or less fragile in this case.
> Or simply do some tests (if ${bindir} != ${sbindir}) and so on.
The tests would get a bit ungainly, since you'd end up with 'if !
[ "${sbindir} = "${bindir}" -o "${sbindir}" = "${base_sbindir}" -o
"${sbindir}" = "${base_sbindir}" ... ]' kind of things. But yes, that
would certainly work as well.
p.
next prev parent reply other threads:[~2012-09-24 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 6:26 [PATCH] staging: Avoid staging the same binaries again and again Phil Blundell
2012-09-24 8:51 ` Richard Purdie
2012-09-24 9:40 ` Phil Blundell
2012-09-24 9:54 ` Richard Purdie
2012-09-24 9:59 ` Phil Blundell [this message]
2012-09-27 21:18 ` Phil Blundell
2012-09-27 21:35 ` Richard Purdie
2012-09-28 10:43 ` Phil Blundell
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=1348480798.31293.26.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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.