From: "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "hsbt (Hiroshi SHIBATA)" <noreply@ruby-lang.org>
Subject: [ruby-core:119394] [Ruby master Feature#20775] Gemify win32-registry, win32-sspi and win32-resolv
Date: Wed, 02 Oct 2024 03:10:30 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-110010.20241002031030.5550@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20775.20241001193658.5550@ruby-lang.org>
Issue #20775 has been updated by hsbt (Hiroshi SHIBATA).
Status changed from Open to Assigned
Assignee set to hsbt (Hiroshi SHIBATA)
>win32-registry
I agreed your proposal.
@nobu Do you have any concern?
>win32-sspi
I'm +1 to @nobu's opinion. we removed it from `ruby/ruby`.
>win32-resolv
As nobu said, we already bundled it to resolv gem.
----------------------------------------
Feature #20775: Gemify win32-registry, win32-sspi and win32-resolv
https://bugs.ruby-lang.org/issues/20775#change-110010
* Author: larskanis (Lars Kanis)
* Status: Assigned
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
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.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/
next prev parent reply other threads:[~2024-10-02 3:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 19:36 [ruby-core:119390] " larskanis (Lars Kanis) via ruby-core
2024-10-02 2:38 ` [ruby-core:119393] " nobu (Nobuyoshi Nakada) via ruby-core
2024-10-02 3:10 ` hsbt (Hiroshi SHIBATA) via ruby-core [this message]
2024-10-02 4:52 ` [ruby-core:119395] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-10-02 8:56 ` [ruby-core:119397] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-10-02 9:27 ` [ruby-core:119398] " larskanis (Lars Kanis) via ruby-core
2024-10-02 9:37 ` [ruby-core:119399] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-10-02 11:47 ` [ruby-core:119400] " nobu (Nobuyoshi Nakada) via ruby-core
2024-10-02 12:31 ` [ruby-core:119403] " larskanis (Lars Kanis) via ruby-core
2024-10-02 13:28 ` [ruby-core:119404] " larskanis (Lars Kanis) via ruby-core
2024-10-04 8:57 ` [ruby-core:119443] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-10-08 8:13 ` [ruby-core:119481] " hsbt (Hiroshi SHIBATA) via ruby-core
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-110010.20241002031030.5550@ruby-lang.org \
--to=ruby-core@ml.ruby-lang.org \
--cc=noreply@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).