[ruby-core:121268] [Ruby master Bug#21095] Prefer `uname -n` over `hostname` in tests.

Issue #21095 has been updated by nagachika (Tomoyuki Chikanaga).

Backport changed from 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: REQUIRED, 3.4: DONE to 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: DONE, 3.4: DONE

ruby_3_3 commit:fff5baf200572762a60c624bc7bea866992c2f30 merged revision(s) commit:46b544c54955348ef1ea9692b837b061f59f91cd, commit:d3abee739f4feb91bb9aaae33877d70c8c576db0.

----------------------------------------
Bug #21095: Prefer `uname -n` over `hostname` in tests.
https://bugs.ruby-lang.org/issues/21095#change-112224

* Author: ioquatix (Samuel Williams)
* Status: Closed
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: DONE, 3.4: DONE
----------------------------------------
It turns out that `hostname`, while a defacto standard, is not actually a standard in any official sense. On Linux, it's distributed as part of the `inettools` package, and while generally available on other platforms (BSD, Windows, MacOS), it isn't actually part of any standard.

The `uname(1)` system call and `uname(2)` command ARE standardised by POSIX and the Open Group, and are included in most base systems without the need to install extra packages (e.g. `inettools` on Linux).

As such, I was requested by the Arch Linux Ruby maintainer, to prefer using `uname -n` as they would like to drop the dependency on `inettools` which has various issues; see <https://gitlab.archlinux.org/archlinux/packaging/packages/inetutils/-/issues/2#note_211062> for more context and background.

I've been asked if this can be back ported to 3.3 and 3.4 and while it's not strictly a bug, it will reduce friction in the distribution channels, so I'd like to propose that we backport to 3.4 and if possible 3.3 too.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- [e-mail]
 To unsubscribe send an email to [e-mail]
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/