Date: Fri, 24 Apr 2015 21:02:18 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Bryan Drewery <bdrewery@FreeBSD.org> Cc: arch@FreeBSD.org Subject: Re: RFC: Alternative to PRIVATELIB Message-ID: <20150424190218.GA13141@ivaldir.etoilebsd.net> In-Reply-To: <553A92DD.1020404@FreeBSD.org> References: <20150411142835.GE65320@ivaldir.etoilebsd.net> <553A922F.3000303@FreeBSD.org> <553A92DD.1020404@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 24, 2015 at 02:00:45PM -0500, Bryan Drewery wrote: > On 4/24/2015 1:57 PM, Bryan Drewery wrote: > > On 4/11/2015 9:28 AM, Baptiste Daroussin wrote: > >> Prefix all manpage with private_ so that we can provide the documentat= ion for > >> the said libs for the version we ship but if another version is shippe= d by ports > >> then we can easily access both documentation. > >> > >=20 > > This sounds useful for debugging and developing base applications which > > need these private libs. >=20 > However I would suggest a /usr/share/man/private that you can access by > setting MANDIR. Prefixing all manpages with 'private_' will get silly > with cross-references and function_name.3 files. Actually manpages is the complicated part of that proposal, so I may do man= pages in a second attempt :) Best regards, Bapt --envbJBWh7q8WU6mo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlU6kzoACgkQ8kTtMUmk6Eyb8wCfeScAle14ah+Xpx/LeM8lHUKT eyIAoLndSPyxLSMpISizRgtxK9B6pqkS =pF6w -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150424190218.GA13141>