From owner-freebsd-ports  Sun Jan 18 20:03:24 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA19699
          for freebsd-ports-outgoing; Sun, 18 Jan 1998 20:03:24 -0800 (PST)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA19690
          for <ports@freebsd.org>; Sun, 18 Jan 1998 20:03:18 -0800 (PST)
          (envelope-from imp@village.org)
Received: from harmony [10.0.0.6] 
	by rover.village.org with esmtp (Exim 1.71 #1)
	id 0xu8Qf-0002Kg-00; Sun, 18 Jan 1998 21:03:17 -0700
Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id VAA02286; Sun, 18 Jan 1998 21:03:16 -0700 (MST)
Message-Id: <199801190403.VAA02286@harmony.village.org>
To: John Fieber <jfieber@indiana.edu>
Subject: Re: Docs for bsd.ports.mk 
Cc: ports@FreeBSD.ORG
In-reply-to: Your message of "Sun, 18 Jan 1998 22:31:55 EST."
		<Pine.BSF.3.96.980118223014.26398Q-100000@fallout.campusview.indiana.edu> 
References: <Pine.BSF.3.96.980118223014.26398Q-100000@fallout.campusview.indiana.edu>  
Date: Sun, 18 Jan 1998 21:03:16 -0700
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In message <Pine.BSF.3.96.980118223014.26398Q-100000@fallout.campusview.indiana.edu> John Fieber writes:
: You mean beyond what www.freebsd.org/handbook/porting.html
: provides? 

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.  The NOCLEANDEPENDS question I
just had, for example.  Also things like PREFIX and alternative
FETCH_CMDs and the like would be good to have as well.

Warner