https://bugs.winehq.org/show_bug.cgi?id=53344
--- Comment #8 from Hans Leidekker hans@meelstraat.net --- (In reply to iLOveBugs from comment #7)
Created attachment 72734 [details] alternative patch proposal, untested
How about this then? Just override the priority string if the user specified a manual override via GNUTLS_SYSTEM_PRIORITY_FILE. Otherwise, leave the existing code logic as is.
Yes, that's better. I would make env_str a global variable however so we don't need to query it twice.
You can't concatenate to env_str like that but why would you? I think it would be better to expect the override to specify the full priority string. The user may want %COMPAT instead of %LATEST_RECORD_VERSION for example.