libgvc6 conflicts against libgvc5. Having different packages per ABI is also done to make them co-installable, which is kind of defeated by this conflict and makes library transitions unnecessary complex. There doesn't seem to be any file conflict, making this conflict arbitrary.
wrong, the plugins conflict. yes, I don't see a good way to upgrade. you could split out the plugins, but then what kind of worth has libgvc5? It's my understanding that the library itself is unusable without the basic plugins.
reopen 755127 thanks Am 19.07.2014 14:18, schrieb Matthias Klose: You don't need to split the plugins, you can put them in a so-versioned directory, e.g. /usr/lib/<packagename> Reopening, since this issue is not fixed.
Am 19.07.2014 14:40, schrieb Michael Biebl: Sure, and keeping the plugins in a directory which probably is not expected by third party plugins. As you like it, however it is not a RC issue, policy 8.1 doesn't require conflict-free upgrades. I prefer the layout as currently done, and will defer any other changes to a new maintainer. Matthias