On 9/8/26 9:42 PM, Rafael Sadowski wrote:
> On Tue Sep 08, 2026 at 08:47:12PM +0200, Volker Schlecht wrote:
>> ... alternatively, here's a simple wrapper around getexecpath(3),
>> with adjusted test cases to document where we deviate from upstream's
>> default behavior - might be harder to upstream once 8.0 is released,
>> but it's worth a shot.
> 
> I like this version better, but do you think upstream will accept it?

I have no idea ... it might break applications that expect a truncated path
instead of an error. Living with that is a choice that is probably easier to 
make for us, than for the libuv project.
It will most probably lead to bug reports about a perceived regression, after 
they just implemented their own solution:

https://github.com/libuv/libuv/commit/71801576eb58da81ed4b9b0c607a36a7f6dd8200

In any case, the behavior of the libuv API seems to be intentional, see:

https://github.com/libuv/libuv/commit/555a9647a079e3a084c19850011112a644651f9a
https://github.com/libuv/libuv/commit/885b1ecda0037fcb6647e8d69a914347ad884244

> Why not just hide the getexecpath(3) handling behind "__OpenBSD__" and leave
> the old version unchanged?
It's happening in a file that's only compiled for OpenBSD ... :-)