Quack, Sorry for the late reply.
You're right DXVK can now handle wine-stable version (5.0.3). I have not tested it but upstream claims 3.10 as the minimum version needed.
That still won't let this package into testing though as it is built against libwine-development-dev that will never reach testing. Without making two separate packages I don't think that would work.
Also, with the important gap between stable and devel versions I'm wondering how DXVK is going to perform. Again without another package built with libwine I don't see how we can be sure that's not gonna break. I personally stopped using the Debian packaged wine-development because they are unable to keep up with the release frequency (and also did not seem willing to accept me in their team to contribute) and I've been using the packages provided on winehq and that never broke so far. That is to say I may have overestimated the risk.
I'm not really interested in creating another package for stable knowing I would never use it myself and thus would not be able to test it, but I'm ok to remove the restrictions on dxvk-setup.
I'll schedule that for the next upload. Regards. \_o< -- Marc Dequènes
