I of course did not read a single patch in files/ :).

But I trust you made sure it works fine.

In D38165#885519, @kai wrote:

• Rebase
• Clean up some comment remnants that were added due debugging purposes

Ping? In the meantime, had anyone else of kde@ been able to test this diff of www/qt5-webengine a bit with some consumers?

sorry for the silence -- I generally assume that your patches work :D

I'll rebuild my repo with it, and will see whether kmail works tomorrow.

In D38165#885649, @tcberner wrote:

I of course did not read a single patch in files/ :).

But I trust you made sure it works fine.

This is understandable, because in files/ lurk several dangers. :)

Ping? In the meantime, had anyone else of kde@ been able to test this diff of www/qt5-webengine a bit with some consumers?

sorry for the silence -- I generally assume that your patches work :D

I'll rebuild my repo with it, and will see whether kmail works tomorrow.

No worries and thank you for the feedback. :)

My only concern was that www/qt5-webengine can be cross-checked for runtime by someone else, to avoid the kind of silly glitches that happened with www/qt6-webengine due a hardcoded path that was overlooked.

If I still hadn't heard anything after the ping, I'd have set the next weekend as an ETA to finally get this diff into the ports tree. :D

P.S.: Regarding the aarch64 platform I cannot give an info if its buildable. Presumably, someone will have to adjust some patches afterwards.

In D38165#885757, @kai wrote:

In D38165#885649, @tcberner wrote:

I of course did not read a single patch in files/ :).

But I trust you made sure it works fine.

This is understandable, because in files/ lurk several dangers. :)

Ping? In the meantime, had anyone else of kde@ been able to test this diff of www/qt5-webengine a bit with some consumers?

sorry for the silence -- I generally assume that your patches work :D

I'll rebuild my repo with it, and will see whether kmail works tomorrow.

No worries and thank you for the feedback. :)

My only concern was that www/qt5-webengine can be cross-checked for runtime by someone else, to avoid the kind of silly glitches that happened with www/qt6-webengine due a hardcoded path that was overlooked.

If I still hadn't heard anything after the ping, I'd have set the next weekend as an ETA to finally get this diff into the ports tree. :D

P.S.: Regarding the aarch64 platform I cannot give an info if its buildable. Presumably, someone will have to adjust some patches afterwards.

so far I did not notice any issue in kmail

so far I did not notice any issue in kmail

Perfect, thanks for your help! I'm going to commit it in a few minutes. :D