On Mon, Jan 9, 2023, at 09:34, Jiri Slaby wrote:
> On 09. 01. 23, 9:14, Jan Engelhardt wrote:
>> On Monday 2023-01-09 08:04, Jiri Slaby wrote:
>
> Right, we used to keep providing also defines and structs in uapi
> headers of removed functionality. So that the above socket would
> compile, but fail during runtime.
>
> I am not biased to any solution. In fact, I found out trinity was fixed
> already. So either path networking takes, it's fine by me. I'm not sure
> about the chromium users, though (and I don't care).
Chromium and some of the others look like automatically generated
lists of files and the rest seem to have compile-time checks.
>From a brief look at all the packages in the debian codesearch
link you provided, I don't see any that are likely to cause
problems aside from trinity.
Arnd
