Feature #20775
openGemify win32-registry, win32-sspi and win32-resolv
Description
Many libraries bundled with ruby have been gemified and were separated into it's own repository.
Not so far the 3 win32 libraries: https://github.com/ruby/ruby/tree/master/ext/win32/lib/win32
- win32/registry
- win32/resolv
- win32/sspi
win32-registry¶
I started with win32/registry in https://github.com/larskanis/win32-registry
- separate all commit into it's own repository,
- make it a gem,
- add proper test cases to verify the core functions,
- add a GHA workflow to run the tests,
- add a single commit to change to consistent UTF-8 string output (see https://bugs.ruby-lang.org/issues/20774)
My intention is that the repository can be moved to https://github.com/ruby/win32-registry and can be integrated it into ruby.
However I think win32/registry
should permanently stay a bundled gem, since the registry access is a core functionality on Windows, so it should always be in the core ruby distribution.
win32-sspi¶
Regarding win32/sspi
I doubt that anyone is using this library.
It was completely broken since ruby-3.0 until some days ago due to this fix: https://github.com/ruby/ruby/commit/fc2f196cb8542a81bf271cdb90e0189c54321103
Nevertheless it makes sense to gemify it and to move it to it's own repository.
I use a massively extended version of this file at work, maybe this can be included then.
IMHO there's no need to keep it in the ruby distribution.
win32-resolv¶
I don't have a strong opinion reg. win32/resolv
and never had a reason to use this platform dependent API instead of the cross platform functions in the socket
library.
Maybe it had a use in the past.