NetBSD Problem Report #57953

From www@netbsd.org  Fri Feb 23 02:58:47 2024
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 3A49B1A9239
	for <gnats-bugs@gnats.NetBSD.org>; Fri, 23 Feb 2024 02:58:47 +0000 (UTC)
Message-Id: <20240223025845.DF2881A923B@mollari.NetBSD.org>
Date: Fri, 23 Feb 2024 02:58:45 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: getnameinfo(3) should have a getnameinfo(1) counterpart like getaddrinfo(3) has getaddrinfo(1)
X-Send-Pr-Version: www-1.0

>Number:         57953
>Category:       bin
>Synopsis:       getnameinfo(3) should have a getnameinfo(1) counterpart like getaddrinfo(3) has getaddrinfo(1)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 23 03:00:01 +0000 2024
>Originator:     Taylor R Campbell
>Release:        current, 10, 9, 8, ...
>Organization:
The NetDB Foundation
>Environment:
>Description:
Some years ago we adopted a getaddrinfo(1) utility to wrap the getaddrinfo(3) C API.

For some reason it didn't occur to me at the time to do the same for getnameinfo(1).
>How-To-Repeat:
codito, ergo sum
>Fix:
Yes, please!

Home	PR Database Search