Bug 8978 - devtool: deploy-target: preserve old files so we can restore them later
Summary: devtool: deploy-target: preserve old files so we can restore them later
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.1
Hardware: All Multiple
: Medium enhancement
Target Milestone: 2.1
Assignee: Paul Eggleton
QA Contact:
URL:
Whiteboard:
Depends on: 7908
Blocks:
  Show dependency tree
 
Reported: 2016-01-21 22:40 UTC by Paul Eggleton
Modified: 2016-02-21 19:46 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2016-01-21 22:40:46 UTC 
When running devtool deploy-target we overwrite any files that were already present on the target. If the target machine isn't running a throw-away image that could be problematic if you were working on some core component of the image. If space allows, we should preserve the files that would have been overwritten and restore them when undeploying. This will need to be done after we move the deployed file list to the target (covered by bug 7908).

As part of this we will also need to add a free space check; at the moment we don't do this. Unfortunately that size check will probably need to be aware that the files being deployed could be across multiple mounted filesystems with separate space pools. 

There should also be an option to skip preserving in case of systems with limited free space where preservation isn't important.