From owner-freebsd-current@FreeBSD.ORG  Wed Apr 23 11:08:44 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1F6A937B401; Wed, 23 Apr 2003 11:08:44 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 55C9743F3F; Wed, 23 Apr 2003 11:08:41 -0700 (PDT)
	(envelope-from eischen@pcnet1.pcnet.com)
Received: from pcnet1.pcnet.com (localhost [127.0.0.1])
	by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h3NI8eBg004196;
	Wed, 23 Apr 2003 14:08:40 -0400 (EDT)
Received: from localhost (eischen@localhost)h3NI8e1v004193;
	Wed, 23 Apr 2003 14:08:40 -0400 (EDT)
Date: Wed, 23 Apr 2003 14:08:40 -0400 (EDT)
From: Daniel Eischen <eischen@pcnet1.pcnet.com>
To: Mike Barcroft <mike@FreeBSD.org>
In-Reply-To: <20030423133153.A35731@espresso.bsdmike.org>
Message-ID: <Pine.GSO.4.10.10304231351310.1203-100000@pcnet1.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Daniel Eischen <deischen@FreeBSD.org>
cc: current@FreeBSD.org
Subject: Re: Multiple (same) sets of man pages
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2003 18:08:44 -0000

On Wed, 23 Apr 2003, Mike Barcroft wrote:

> Daniel Eischen <deischen@freebsd.org> writes:
> > [ doc@ bcc:'d ]
> > 
> > With 3 threading libraries, each with a set of the same man pages,
> > how should this be handled?  It doesn't make any sense to have
> > all of them installed and yet it should still be possible to
> > install all 3 thread libraries.
> > 
> > Do we need a different heirarchy for threads?
> 
> Ideally, they'd all document the same specification.  Perhaps there

Right, but there may be extensions in some that aren't in the
others.  So those would be library-specific man pages.  Like
pthread_switch_{add,delete}_np() that I believe is only supported
in libc_r.  I have no plans on supporting it in libpthread
since it really doesn't make sense there.  There will also be
other functions available in libpthread that aren't in libc_r
(and perhaps libthr).

> would be one document that discusses the pros and cons of each
> implementation with instructions on enabling them.

Right, I think an overall 'man threads' should give you that.
Eventually, libc_r should be deprecated so placing the common
man pages in there doesn't make sense.  Of course we can ignore
it until we get to that point.

I've currently got the man pages commented out of libpthread's
Makefile 'cause it doesn't make sense to install them over
those installed by libc_r.  I'm just raising the issue; I'll
do whatever the doc guys recommend.

-- 
Dan Eischen