diff options
| author |   Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-05-19 08:51:24 +1200 |
|---|---|---|
| committer | Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-05-30 16:01:42 +1200 |
| commit | 48c0839482023832ce00a12c9c78f74d14fce6c5 (patch) | |
| tree | 0e73d86e3041117e51340e496b2a6d53b76f207b /layerindex/update.py | |
| parent | b80833e1c9d2e8d4bd15903810bc981dd3a9c19e (diff) | |
| download | openembedded-core-contrib-48c0839482023832ce00a12c9c78f74d14fce6c5.tar.gz | |
Allow blanking out field values in bulk change
If you're moving a short description value from DESCRIPTION to SUMMARY
then part of that is setting DESCRIPTION to blank, however that wasn't
possible - the code was assuming that a null value meant "keep the
original value". Change the logic so that the value in the bulk change
object is always set and is compared to the original value to see if it
is different. This provides less safety against bulk change data going
stale in the face of the metadata being updated, but without using an
additional "magic" field value that's the price we have to pay, and it's
unlikely to bother too many people I would imagine.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Diffstat (limited to 'layerindex/update.py')
0 files changed, 0 insertions, 0 deletions