https://bugs.winehq.org/show_bug.cgi?id=49199
--- Comment #2 from Gcenx gcenx83@gmail.com --- (In reply to Alexandre Julliard from comment #1)
I'm not sure what "embedded dylibs" means, or how they were getting loaded from /lib in the first place, but it sounds like a packaging issue.
Wine-5.5 and below would check its own /lib(64) directly for any required dylibs before checking standard system locations
Each .so would check @loader_path/../ meaning it would check for and use any embedded dylibs, this is desirable to allow wine to be relocatable.
Here is an explanation; ${wine_path}/lib/wine/gdi32.so would precisely check back one directory, that behavior was desirable as the required dylib could be placed into ${wine_path}/lib where it would be loaded reguardless of the current path.
I don’t see how this would be considered a picking issue when this was the previous behavior before these changes.