From owner-freebsd-ports@FreeBSD.ORG Sun Jan 4 19:40:27 2009 Return-Path: Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0251106564A for ; Sun, 4 Jan 2009 19:40:27 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id 6F4068FC1A for ; Sun, 4 Jan 2009 19:40:27 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.3/8.14.3) with ESMTP id n04JeRAU043988 for ; Sun, 4 Jan 2009 11:40:27 -0800 (PST) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.3/8.14.3/Submit) id n04JeRYo043987 for freebsd-ports@FreeBSD.ORG; Sun, 4 Jan 2009 11:40:27 -0800 (PST) (envelope-from david) Date: Sun, 4 Jan 2009 11:40:27 -0800 From: David Wolfskill To: FreeBSD Ports List Message-ID: <20090104194027.GC4100@albert.catwhisker.org> References: <20090104172542.GA11950@teddy.fas.com> <20090104173644.GA4100@albert.catwhisker.org> <20090104193330.GA14428@teddy.fas.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Bi1c4c+m8JUixgIF" Content-Disposition: inline In-Reply-To: <20090104193330.GA14428@teddy.fas.com> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: A question about the rrd tools port X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2009 19:40:27 -0000 --Bi1c4c+m8JUixgIF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 04, 2009 at 02:33:30PM -0500, stan wrote: > ... > > It looks to me as if at least some of the man pages installed by rrdtool > > do not have corresponding executables because they are purely > > documentation: e.g., bin_dec_hex; cdeftutorial; rpntutorial; > > rrdgraph_examples. >=20 > OK, here is an example of what I am asking about "rrdrestore". The functi= on > can be done with rrdtool import, but why is tere a man page, if there is > not intended to be an executable, or a llink? That's a different case from the examples I cited above. Like cvs(1), rrdtool(1) is a single executable that takes several different (sub)commands. Unlike cvs(1) (and like perl(1)), the way the rrdtool(1) man pages are arranged involves having separate man pages for each subcommand (or other aspect of rrdtool that the author or contributors wished to document). E.g., the man page is called "rrdrestore", but as the SYNOPSIS of that man page shows, it is invoked as "rrdtool restore ...." Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --Bi1c4c+m8JUixgIF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklhEKoACgkQmprOCmdXAD1nlQCfTFJUD4XvEtyRc6Suv8PiBCPg KdgAn0KMSY9PVff7P9pD/5RcQ9871KXi =OOqM -----END PGP SIGNATURE----- --Bi1c4c+m8JUixgIF--