From owner-freebsd-ports  Sun Jan 18 20:06:31 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA19977
          for freebsd-ports-outgoing; Sun, 18 Jan 1998 20:06:31 -0800 (PST)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA19968
          for <ports@FreeBSD.ORG>; Sun, 18 Jan 1998 20:06:23 -0800 (PST)
          (envelope-from jfieber@indiana.edu)
Received: from localhost (jfieber@localhost)
	by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id XAA10329;
	Sun, 18 Jan 1998 23:06:18 -0500 (EST)
Date: Sun, 18 Jan 1998 23:06:17 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Warner Losh <imp@village.org>
cc: ports@FreeBSD.ORG
Subject: Re: Docs for bsd.ports.mk 
In-Reply-To: <199801190403.VAA02286@harmony.village.org>
Message-ID: <Pine.BSF.3.96.980118230412.26398T-100000@fallout.campusview.indiana.edu>
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, Warner Losh wrote:

> Yes.  Right now the porting.html talks about writing a port.  It is
> excellent for writing a port.  However, there are many dirty tricks
> that have been used for building ports.

Ah, yes.  I guess I missed the intent of your post.  A port USERS
guide would be a most welcome addition.

-john