I'm seriously afraid of introducing a security hole with this change, so I highlighted places in the code I'm not sure about.

• More TODOs

If I understand it correctly, this change does not affect nextboot either?

I don't see a point in doing this. You shouldn't run make cabal-extract and friends on quarerly branches.

Fixed too.

Fixed in 87a12423c24377eb05ab20aa44897ecd443c0f9e

How do I reproduce the problem?

This change is still not merged in.

LGTM, thanks for working on this! Note that multimedia/wireplumber would benefir from the update too.

GitLab MR URLs aren't stable:

=> Attempting to fetch https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/2738.patch
fetch: https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/2738.patch: size unknown
fetch: https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/2738.patch: size of remote file is not known
2738.patch                                            1694  B   13 MBps    00s
=> Fetched file size mismatch (expected 1415, actual 1694)

You can just cat all these patches into a giant one and put it under files/, though.

Works for me!

In D55539#1273814, @kib wrote:

In particular, I believe that you should not see the problem e.g. on tmpfs, am I right?

In D55539#1272422, @kib wrote:

Are you sure that it was EINVAL? EINVAL path should not result in such condition.

I found a case where EEXISTS could do it, and hopefully fixed.

The last revision worked for me on ZFS.

• Don't use MAKE_JOBS for do-build and add an explaining comment

Is my understanding correct that it is not supposed to work with ZFS yet?

It is always a pleasure to merge a well-formed port update with a passing test suite. Kudos to Dave for preparing this change.

Makes sense to me too, but the last word is portmgr 's.