Date: Tue, 29 Apr 2003 22:18:56 -0500 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: "W. Josephson" <cvs-D20030429@morphisms.net> Cc: Dag-Erling Smorgrav <des@ofug.org> Subject: Re: cvs commit: src/lib/libc/gen check_utility_compat.c confstr.c fmtmsg.c getgrent.c getpwent.c src/lib/libc/include namespace.h un-namespace.h src/lib/libc/locale setlocale.c src/lib/libc/net getaddrinfo.c gethostbydns.c getnameinfo.c hesiod.c ... Message-ID: <20030430031856.GA20258@madman.celabo.org> In-Reply-To: <20030430004907.GA32349@mero.morphisms.net> References: <200304292113.h3TLDoGF072965@repoman.freebsd.org> <xzp65oxrn3e.fsf@flood.ping.uio.no> <20030430002014.GA1190@dragon.nuxi.com> <xzpptn4rfww.fsf@flood.ping.uio.no> <20030430004907.GA32349@mero.morphisms.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 29, 2003 at 08:49:07PM -0400, W. Josephson wrote: > I guess I don't see the need for a special case > even for strlcpy: why can't ports patch qpopper? The qpopper port maintainer _can_ and _should_ patch qpopper, as well as reporting the bug to the software vendor. I chose to hide strlcpy/strlcat anyway because I am far from certain that qpopper is the only application supplying its own (working or not) implementations. We don't want to call those from within libc, ever. It is too risky. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030430031856.GA20258>