`Hiding' libc symbols

[Jacques A. Vidrine]

On Thu, May 01, 2003 at 02:05:49PM -0400, John Baldwin wrote:
> Agreed.  Somebody just needs to sit down and fix the qpopper port and
> then the argument for this change goes away and it can be reverted.

qpopper is not the point.  The qpopper port was fixed just a couple of
hours after I made the commit to libc.  (I had sent the qpopper patch
to the port maintainer earlier.)  Preventing the bogus behavior from
ever happening again was the point.

A lot of folks are focused on qpopper and strlcpy.  I believe that
the big picture is being missed.  I moved this thread to freebsd-arch
so that we could discuss how to hide all (or most, or non-standard)
symbols in libc.  Not so that we could argue about this particular
commit.

I'm backing out the commit in good faith and in the hopes that the
big picture comes more clearly into focus.  However, I must admit
some disappointment in the situation.  I believe that this was a good
change, one that we need, and one that we should see more of.

Cheers,
-- 
Jacques Vidrine   . NTT/Verio SME      . FreeBSD UNIX       . Heimdal
nectar at celabo.org . jvidrine at verio.net . nectar at freebsd.org . nectar at kth.se