Made lensfun lookups for one lens really unique.  Fixes bug #9662.
Add keywords, as recommended here:

 http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s05.html,
 http://bugs.debian.org/693918, and
 https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords
Keywords value MUST end with a semicolon
Don't switch group if module activated via hotkey is already visible
Exposure IOP: Deflicker (port from Magic Lantern)
Mark internal functions as static
interpolation: OpenCL implementation of interpolation_resample

implementation with naive 1:1 copy of CPU code. as to be expected this is
slow as hell combined with a huge workload on the gpu
Merge branch 'master' into interpolation
Merge pull request #421 from bronger/master

Made lensfun lookups for one lens really unique.  Fixes bug #9662.
Merge branch 'master' into interpolation
opencl, interpolation: a bit less naive implementation
Try to limit network traffic of map view

There is no reason to keep a connection to a map server when dt is not
in map view. This should be relevant for bug #9816.
opencl, interpolation: make better use of local memory

speed wise this should now be ahead of the CPU code
opencl, interpolation: small fix and some added comments
Removed check for ambiguous return values for lens lookups.

It can *never* be guaranteed that the return list of lenses of lensfun contains
only one entry, even if the lens model name was exactly correct.  Lenses with a
longer lens name (containing the shorter one) will also be returned.  However,
it is guaranteed that the exact match will be returned as the zeroth list
element.
Merge pull request #469 from bronger/fix_short_lens_names

Removed check for ambiguous return values for lens lookups.
protection against out of memory in masks

more potential fix for #9808
rawspeed: crop garbage pixels for ILCE-7(R) Bug#9818
(cherry picked from commit d9577e4157705012bc64d80279e4f2ced2cd0238)
rawspeed: nikon d5300
(cherry picked from commit d304f2955a515e1dbdd3297f8d0571c1decc8cd2)
Bug 9807: Correct Olympus Focus Distance

Originally the Focus Distance seems to be stored in a Rational (Fractional) format.

There seems to be some confusion about where the stored value is in centimeters versus millimeters.

This confusion seems to stem from the fact that some implementations seem to ignore the denominator of 10,
using the numerator directly (and incorrectly).

Exiv2's toFloat function properly divides the numerator by the denominator when outputting a Float (as centimeters).

So we need to divide by 100 to get meters.
(cherry picked from commit e32e81be92e8cfba9b728b272828da2173e8b3fc)