On Tue Oct 7 09:42:24 2025 +0000, Ratchanan Srirattanamet wrote:
Well... to be honest I'm not sure how likely a user will install an application (and its dependencies), found out that it doesn't work, and then try again with upgraded Wine but the same $WINEPREFIX. It's also possible that a user doesn't really know about $WINEPREFIX at all... But you do have a point in that the user might miss it anyway. So the question now becomes "what should we do in this case?". Should we simply return `ERROR_BAD_CONFIGURATION` silently? Or should we simply pass the first feature? Should we issue a warning/error in this case? Should we cross-check this behavior with Windows?
We can return ERROR_CALL_NOT_IMPLEMENTED here with a FIXME like `"Product has multiple features but the published assembly record doesn't have a feature"` which would let us know what's going on and help the user.
ERROR_CALL_NOT_IMPLEMENTED is what used to be returned so this shouldn't cause any change in behavior.