diff options
author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2015-06-16 17:16:51 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-06-18 09:12:01 +0100 |
commit | 69adaed0e982d627ebfa57b360b0ee049ea7a276 (patch) | |
tree | 823b6d60df575b8026d2f70e2c722837d0ca2f9e /meta-selftest/README | |
parent | ff720dd3b77130b2c485d7acad63735fd8751a7d (diff) | |
download | openembedded-core-69adaed0e982d627ebfa57b360b0ee049ea7a276.tar.gz openembedded-core-69adaed0e982d627ebfa57b360b0ee049ea7a276.tar.bz2 openembedded-core-69adaed0e982d627ebfa57b360b0ee049ea7a276.zip |
devtool: deploy: fix preservation of symlinks and permissions/ownership
It turns out that scp can't be used to copy symlinks because it follows
them instead of copying them, and this is by design (since it emulates
rcp which also behaved this way); the unfortunate result is that
symlinks that point to valid files on the host translate into the host
file being copied to the target (yuck). The simplest alternative that
does not have this undesirable behaviour is to use tar and pipe it over
ssh.
At the same time, it would be even better if we properly reflect file
permissions and ownership on the target that have been established
within the pseudo environment. We can do this by executing the copy
process under pseudo, which turns out to be quite easy with access to
the pseudo environment set up by the build system.
Fixes [YOCTO #7868].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Diffstat (limited to 'meta-selftest/README')
0 files changed, 0 insertions, 0 deletions