Bug#886052: ogmrip: GSettings migration happened upstream

[Yavor Doganov]

tags 886052 + fixed-upstream
thanks

You are probably aware that GSettings support is available in the
upstream Git repository.  I successfully built the master branch and
couldn't detect any problems (except that old settings are not
migrated), although I can't test properly as I don't have a DVD.

Unfortunately this migration (plus some other major refactoring)
caused ABI break but the SONAME wasn't bumped.  Some libraries
disappeared entirely, others were renamed and the API changed
significantly.  Patches for the GSettings switch are not
cherry-pickable because a large chunk of the history is lost.  But
even if they would, they would still break the ABI beacuse of the way
GConfClient is wrapped in another object (OGMRipSettings), with a
non-trivial abstraction layer around profile parsing/loading and
mapping the elements to the corresponding GConf keys.

So you might want to ask your upstream to make a new release with
SONAMEs of all libraries bumped.  Alternatively, package a snapshot of
the Git repo and install all libraries as private.  There are no rdeps
in Debian and AFAICT all binary packages can be merged into one
(ogmrip-plugins is particularly useless because ogmrip depends on it).