Hello,
I'm planning to add the following line to apisetschema.spec:
*api-ms-win-power-setting-l1-1-1 = powrprof.dll*
However, this causes a hash conflict with the existing line:
*apiset api-ms-win-power-setting-l1-1-0 = powrprof.dll*
May I ask how you usually resolve such conflicts?
I'm concerned that removing version 1-0 might cause some older applications to stop working.
Would it be possible to delete the router for 1-0 and instead add a new line like this?
*ln -s powrprof.dll api-ms-win-power-setting-l1-1-0*
Hello,
For calculating the hash the last digit is intentionally ignored, so you will always get a hash collision. Although I didn't find any official documentation, the last digit seems to be the minor version, and I'd assume that means it remains backwards compatible. Unless you get someone more experienced to answer, I'd probably submit that as PR and see what Alexandre says.
Regards, Fabian Maurer
zhengxianwei baikaishiuc@gmail.com writes:
Hello,
I'm planning to add the following line to apisetschema.spec:
api-ms-win-power-setting-l1-1-1 = powrprof.dll
However, this causes a hash conflict with the existing line:
apiset api-ms-win-power-setting-l1-1-0 = powrprof.dll
May I ask how you usually resolve such conflicts?
The last version number is ignored, l1-1-0 and l1-1-1 mean exactly the same thing, you don't need to change anything.
Fixed!
Cool, Thanks
On Sat, May 17, 2025 at 9:48 PM Alexandre Julliard julliard@winehq.org wrote:
zhengxianwei baikaishiuc@gmail.com writes:
Hello,
I'm planning to add the following line to apisetschema.spec:
api-ms-win-power-setting-l1-1-1 = powrprof.dll
However, this causes a hash conflict with the existing line:
apiset api-ms-win-power-setting-l1-1-0 = powrprof.dll
May I ask how you usually resolve such conflicts?
The last version number is ignored, l1-1-0 and l1-1-1 mean exactly the same thing, you don't need to change anything.
-- Alexandre Julliard julliard@winehq.org