From owner-freebsd-ports  Sat Aug 26 04:51:52 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id EAA14236
          for ports-outgoing; Sat, 26 Aug 1995 04:51:52 -0700
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id EAA14230
          for <ports@freebsd.org>; Sat, 26 Aug 1995 04:51:50 -0700
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id EAA28902; Sat, 26 Aug 1995 04:51:44 -0700
To: asami@cs.berkeley.edu (Satoshi Asami)
cc: ports@freebsd.org
Subject: Re: `make info'? 
In-reply-to: Your message of "Sat, 26 Aug 1995 04:34:32 PDT."
             <199508261134.EAA02000@silvia.HIP.Berkeley.EDU> 
Date: Sat, 26 Aug 1995 04:51:44 -0700
Message-ID: <28899.809437904@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: ports-owner@freebsd.org
Precedence: bulk

> Uhh, GUIDELINES was for porters, not users...so this system is not
> going to "replace" it....

You misunderstand me.  If you're going to go to a "meta README" deal,
then you're going to have a chance to do more than talk about invoking
rules like `info' (and `build' and `install', please!), you'll be able
to point to the URL of the ports guidelines section of the handbook.
Those so inclined can follow it.  Problem solved.

In fact, while we're at it, why not also do the README in HTML?  It'd
still be human readable if you were careful about imbeding the
formatting statements unobtrusively (no AREFs in the middle of
paragraphs, just down in a summary bar on the bottom of the page).
Then we can automate a little CGI tree-walker for the ports directly
from the web.

					Jordan