From owner-freebsd-current@FreeBSD.ORG  Wed Apr 23 10:46:38 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 F384337B401; Wed, 23 Apr 2003 10:46:37 -0700 (PDT)
Received: from espresso.bsdmike.org (espresso.bsdmike.org [65.39.129.122])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id E9E1243FDF; Wed, 23 Apr 2003 10:46:36 -0700 (PDT)
	(envelope-from mike@espresso.bsdmike.org)
Received: by espresso.bsdmike.org (Postfix, from userid 1002)
	id 441699C4C; Wed, 23 Apr 2003 13:31:53 -0400 (EDT)
Date: Wed, 23 Apr 2003 13:31:53 -0400
From: Mike Barcroft <mike@FreeBSD.org>
To: Daniel Eischen <deischen@freebsd.org>
Message-ID: <20030423133153.A35731@espresso.bsdmike.org>
References: <3EA5AC88.83535AE6@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3EA5AC88.83535AE6@freebsd.org>;
	from deischen@freebsd.org on Tue, Apr 22, 2003 at 04:56:40PM -0400
Organization: The FreeBSD Project
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 17:46:38 -0000

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
would be one document that discusses the pros and cons of each
implementation with instructions on enabling them.

Best regards,
Mike Barcroft