[ruby-core:103947] [Ruby master Feature#17873] Update of default gems in Ruby 3.1

[knu@ruby-lang.org]

Issue #17873 has been updated by knu (Akinori MUSHA).


I don't see a good reason to remove the syslog library from ruby.
It is so small, simple, and almost maintenance-free because the syslog facility is unlikely to change anymore.

Syslog has long been a standard logging facility in Unix/Linux and I believe it is good for ruby to have access to it out of the box.
I can imagine it is used by many admins in their system scripts.

Also, there seem to be many gems that load `syslog`.
```
knu@aluminium:~$ gem-codesearch "^ *require ['\"]syslog[/\"']"  | ruby -ne 'puts $_.split("/")[3]' | sort -u | wc -l
259
```



----------------------------------------
Feature #17873: Update of default gems in Ruby 3.1
https://bugs.ruby-lang.org/issues/17873#change-92078

* Author: hsbt (Hiroshi SHIBATA)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
I promoted many standard libraries to the default gems. You can see them at https://stdgems.org/#default-gems-ruby-301

I propose the following libraries to promote the bundled gems from the default gems.

```
matrix
prime
net/ftp
net/smtp
net/pop
net/imap
```

They have primary maintainer in the canonical repository in github. So, they can release the new version with their convenience. 

@shugo @marcandre Any thought?

And I also propose to extract the following libraries from the default gems.

```
tracer
dbm
gdbm
syslog
```

They are no longer actively maintained and not widely used today.




-- 
https://bugs.ruby-lang.org/