From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 1/2] image.bbclass, kernel.bbclass: create warning file about deleting deploydir files
Date: Tue, 23 Aug 2011 11:37:20 +0100 [thread overview]
Message-ID: <1314095840.6733.334.camel@phil-desktop> (raw)
In-Reply-To: <201108231032.19140.paul.eggleton@linux.intel.com>
On Tue, 2011-08-23 at 10:32 +0100, Paul Eggleton wrote:
> On Tuesday 23 August 2011 10:22:12 Phil Blundell wrote:
> > Irrespective of whether it happens to work or not on some or other
> > distro, "cp -n" isn't POSIX and we shouldn't be relying on it.
> >
> > I can't really see why the -n option is needed here anyway. It looks to
> > me like it could just be removed with no ill effects.
>
> Sorry, I wasn't aware that it was a non-standard option. I'll post a new
> version with it removed.
Yeah, POSIX cp only understands quite a restricted set of options. It
supports -f, -i, -p, -R, plus -H, -L and -P in newer versions (and the
obsolescent -r). Anything beyond that is not guaranteed.
p.
next prev parent reply other threads:[~2011-08-23 10:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 18:37 [RFC PATCH 0/2] Couple of fixes to help new users Paul Eggleton
2011-08-17 18:37 ` [RFC PATCH 1/2] image.bbclass, kernel.bbclass: create warning file about deleting deploydir files Paul Eggleton
2011-08-17 18:41 ` Phil Blundell
2011-08-19 10:27 ` Paul Eggleton
2011-08-23 19:08 ` Darren Hart
2011-08-23 20:07 ` Paul Eggleton
2011-08-23 21:39 ` Koen Kooi
2011-08-23 21:52 ` Paul Eggleton
2011-08-22 21:01 ` Koen Kooi
2011-08-23 6:44 ` Anders Darander
2011-08-23 8:33 ` Koen Kooi
2011-08-23 9:22 ` Phil Blundell
2011-08-23 9:32 ` Paul Eggleton
2011-08-23 10:37 ` Phil Blundell [this message]
2011-08-17 18:37 ` [RFC PATCH 2/2] sanity.bbclass: add optional untested host distro warning Paul Eggleton
2011-08-23 15:14 ` [RFC PATCH 0/2] Couple of fixes to help new users Saul Wold
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=1314095840.6733.334.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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.