Date: Wed, 23 Apr 2003 21:19:43 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: Daniel Eischen <eischen@pcnet1.pcnet.com> Cc: current@freebsd.org Subject: Re: Multiple (same) sets of man pages Message-ID: <20030423181943.GB52765@sunbay.com> In-Reply-To: <Pine.GSO.4.10.10304231351310.1203-100000@pcnet1.pcnet.com> References: <20030423133153.A35731@espresso.bsdmike.org> <Pine.GSO.4.10.10304231351310.1203-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--GID0FwUMdk1T2AWN
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Apr 23, 2003 at 02:08:40PM -0400, Daniel Eischen wrote:
> On Wed, 23 Apr 2003, Mike Barcroft wrote:
>=20
> > Daniel Eischen <deischen@freebsd.org> writes:
> > > [ doc@ bcc:'d ]
> > >=20
> > > 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.
> > >=20
> > > Do we need a different heirarchy for threads?
> >=20
> > Ideally, they'd all document the same specification. Perhaps there
>=20
> 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).
>=20
> > would be one document that discusses the pros and cons of each
> > implementation with instructions on enabling them.
>=20
> 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.
>=20
> 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.
>=20
Since libpthread and libthr aren't getting built by default,
this is a minor issue now. If you're about to enable either
one or both, the one that is not optional (libc_r is optional)
should get the common manpages. If all libraries are optional,
either one (most commonly used) could get the manpages, and
others should have .PATH to them. Another issue is the .Lb
call in these manpages. They should be fixed to give all three
libraries. I will have to fix the .Lb macro first to make
this work.
Cheers,
--=20
Ruslan Ermilov Sysadmin and DBA,
ru@sunbay.com Sunbay Software AG,
ru@FreeBSD.org FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
--GID0FwUMdk1T2AWN
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+ptk+Ukv4P6juNwoRAtNXAJ9jzCGuNcHLO7Zgd+uNQpo5aNavjQCfXYK4
Z1QwkVfP87UZtkn6q0ND98Y=
=tyKX
-----END PGP SIGNATURE-----
--GID0FwUMdk1T2AWN--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030423181943.GB52765>