Bug#822612: python3-pyatspi: depends on libatk-adaptor and libgail-common

[Emilio Pozuelo Monfort <pochu@debian.org>]

On 26/04/16 02:07, Samuel Thibault wrote:
> Hello,
> 
> Emilio Pozuelo Monfort, on Mon 25 Apr 2016 17:48:02 +0200, wrote:
>> Do you think demoting libgail-common and libatk-adaptor to Recommends would
>> be fine at this stage, so that they are installed by default but can be
>> removed if desired (e.g. if/when there are no gtk2 apps installed)?
> 
> That's a possibility. But we can also do like for qt4: since
> accessibility is now supposed to be enabled by default, we could
> make libgtk2.0-0 itself depend on libgail-common, i.e. the toolkit
> itself makes sure it has the tools to make itself accessible.  That
> way, libgail-common will get installed whenever a gtk2 application is
> installed for some reason.

I'd like that. However that creates a dependency loop as libgail-common depends
on libgail18 which depends on libgtk2.0-0.

Folding libgail into libgtk isn't an option as they don't necessarily keep the
same soname.

Any ideas?

>> These pull libatk-bridge and libgail-common, which depend on
>> libgail18, which depends on libgtk2.0-0.
> 
> Libatk-bridge doesn't actually depend on libgail18, so we can remove its
> dependency on libgail-common, provided that libgtk2.0-0 depends on it.

OK.

Cheers,
Emilio