Am 18.07.2014 um 18:16 schrieb Bill Allombert:
> On Mon, Jul 14, 2014 at 10:43:39AM +0200, Patrick Matthäi wrote:
>>
>> Am 12.07.2014 23:31, schrieb Bill Allombert:
>>> Package: libmlt++3
>>> Version: 0.9.2-1
>>> Severity: important
>>>
>>> Hello Fathi,
>>>
>>> There is a circular dependency between libmlt++3 and libmlt6:
>>>
>>> libmlt++3 :Depends: libmlt6 (>= 0.9.2)
>>> libmlt6 :Depends: libmlt++3 (>= 0.9.2)
>>
>> Right :/
>>
>>> Circular dependencies between shared library are known to cause problems
>>> during
>>> upgrade, so we should try to avoid them.
>>>
>>> Cheers,
>> I did not had problems with them, yet.
>> The question is: what to do here? Both are required (added by
>> ${shlibs:Depends}).
>
> You could simply merge libmlt6 and libmlt++3 in a single package since anyway
> the users need to install both.
Right, but they are different libraries with a different ABI.
>
> The current situation means that the ABI of libmlt6 and libmlt++3 are linked,
> which is dangerous if libmlt++3 soname get bumped but not libmlt6
Never made problems in the past.
>
> So you might need to move the plug-ins to a separate package.
>
> However, as far as I see, only mlt/libmltqt.so require libmlt++3, so maybe
> there is a better way to split the package.
Splitting the plugins into a seperate package would make sense, but it
would introduce new problems:
=> Plugins shlibs:Depends on libmlt6 and/or libmlt++3
=> libmlt++3/libmlt6 are mostly useless without the plugins, so they
should depend on it, too..
For the latter case we could say that applications should also depend on
libmlt-plugins (not libmlt{++3,6) itself), but that is also not such a
nice solution.
--
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/
signature.asc
Description: OpenPGP digital signature
