From owner-freebsd-ports Tue Jan 20 16:28:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21795 for freebsd-ports-outgoing; Tue, 20 Jan 1998 16:28:53 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from ppp7249.on.bellglobal.com (ppp7249.on.bellglobal.com [206.172.249.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21788 for ; Tue, 20 Jan 1998 16:28:42 -0800 (PST) (envelope-from ac199@hwcn.org) Received: from localhost (tim@localhost) by ppp7234.on.bellglobal.com (8.8.8/8.8.8) with SMTP id XAA00460; Sun, 18 Jan 1998 23:49:48 -0500 (EST) (envelope-from ac199@hwcn.org) X-Authentication-Warning: ppp7234.on.bellglobal.com: tim owned process doing -bs Date: Sun, 18 Jan 1998 23:49:46 -0500 (EST) From: Tim Vanderhoek X-Sender: tim@localhost Reply-To: ac199@hwcn.org To: "Jordan K. Hubbard" cc: Warner Losh , John Fieber , ports@FreeBSD.ORG Subject: Re: Docs for bsd.ports.mk In-Reply-To: <3284.885184009@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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.