This was from when Wine 6.5+ and Wine 6.8+ broke several common plugins
in some ways. At least on my system the effected plugins seem to work
fine with wine-tkg 6.19.
We still need the notice about Wine 6.15 and 6.16 though because the
Arch repos still haven't updated beyond 6.16.
This is a bit of a mess (which is also why I kept procrastinating on
this), since we also need to keep symlinks, trailing slashes, and weird
unnormalized paths into account.
In some cases you wouldn't get anything if the font is missing, but in
other cases the fontconfig fallback gets used which may not have the
exact same dimensions as the original font.
Apparently these arguments are all passed as a space separated Win32
command line, so we need to do our own quoting. I was about to submit a
patch for this to Wine, but escaping escaped quotes sounds like a pain.
The difference in performance won't be noticable, but both lookups and
modifications in these things are much faster once you have more than
one or two elements.
This should not be causing any issues, but it seems like some people
skip the locale setup step in the Arch installation guide and then end
up with a distro without any locales, with invalid locales, or with a
non-generated locale. glibc and libstd++ fall back to the C locale when
this happens, but Boost.Process triggers one of the edge cases where
this doesn't happen. https://github.com/boostorg/process/pull/179 fixes
this in Boost.Process, but it will be a while until this is in every
distro's copy of Boost.
https://svn.boost.org/trac10/changeset/72855
We apparently didn't do that yet. SysEx should be super rare (outside of
octave switching on Arturia keyboards), but there's still no reason not
to do it.
This is now even more of a mess, because for some reason the codename
suffix changed again with Wine 6.17. To keep this compact, we now just
add the `-1` suffix for Wine 6.1 to Wine 6.17, and the `-2` suffix for
Wine 6.17 and above.
While we're add it, might as well add another variant to make it easier
to install an older version of `winehq-stable` or `winehq-devel`, if you
for some reason would want to do that.
So far there have been only two blank issues that didn't fall in one of
the three categories we have templates for, and people quite often skip
t he entire template if it's optional, so this will probably make the
issues much more useful.
Robbert van der Helm