Date: Sun, 18 Jan 1998 23:49:46 -0500 (EST) From: Tim Vanderhoek <ac199@hwcn.org> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: Warner Losh <imp@village.org>, John Fieber <jfieber@indiana.edu>, ports@FreeBSD.ORG Subject: Re: Docs for bsd.ports.mk Message-ID: <Pine.BSF.3.96.980118234313.260B-100000@localhost> In-Reply-To: <3284.885184009@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 Jan 1998, Jordan K. Hubbard wrote:
> Perhaps the best solution is to revamp the web docs until they're a
> bit less confusingly organized and also cover more of the details.
> Then write a man page which tries to give the ports collection in
> overview and simply refers to various URLs for the "meaty" stuff.
I think you've got it backwards. :) The web docs are good when
a thorough reading & understanding is required. A manpage is
best for a quick reference (eg. "What was the dang cc(1) arg to
make all warning fatal!?").
I don't like having to fire-up an html browser and navigate
through a series of hyper-links unnecessarily. :)
> Then you'd only really have the web pages to maintain as the ports
> collection evolved and the man page would stay largely change-proof.
I don't think there's too much precedent for changes in the
simple things Warner would be documenting.
--
tIM...HOEk
OPTIMIZATION: the process of using many one-letter variables names
hoping that the resultant code will run faster.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980118234313.260B-100000>