[Development] Orphan modules

[Tor Arne Vestbø]

> On 12 Sep 2018, at 18:52, Lisandro Damián Nicanor Pérez Meyer <perezmeyer at gmail.com> wrote:
> 
> El miércoles, 12 de septiembre de 2018 12:38:03 -03 Thiago Macieira escribió:
>> On Wednesday, 12 September 2018 01:44:36 PDT Gatis Paeglis wrote:
>>>> With the proposed solution of making platform plugins libraries with
>>>> their
>>>> own private headers, we can have these apis closer to the platform code,
>>>> and without lots of plumbing and indirection. I think the qtmacextras
>>>> module in particular should be deprecated ASAP, and will strongly oppose
>>>> any new APIs added to it.
>>> 
>>> +1 for deprecating qtx11extras as well and moving the code closer to
>>> actual
>>> plugin. It is frustrating to have all that boilerplate code for 1 header
>>> file - qx11info_x11.h
>> 
>> I was going to say we needed replacement API for it, but I realise the
>> QX11EmbedContainer is not there. Since people have lived for the last 6
>> years without it in Qt 5, it doesn't seem we really need a replacement.
>> 
>> What do applications do if they need to XEmbed another application's window
>> (for example, VirtualBox for the guest window)? And how do they find out the
>> real pixel size of it, in case scaling is active?
> 
> After reading this I thought of checking which packages would need to be 
> modified in Debian if for some reason qtx11extras ceased to exist. The list is 
> not precisely small:

Does that list guarantee that the package actually uses APIs from the module?

If they do, does the list say anything about whether or not those APIs have modern replacements in Qt or other ways to do the same?

Tor Arne