From owner-freebsd-ports Sun Jan 18 20:09:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA20170 for freebsd-ports-outgoing; Sun, 18 Jan 1998 20:09:14 -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 UAA19900 for ; Sun, 18 Jan 1998 20:05: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 0xu8SY-0002Kn-00; Sun, 18 Jan 1998 21:05:14 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id VAA02310; Sun, 18 Jan 1998 21:05:12 -0700 (MST) Message-Id: <199801190405.VAA02310@harmony.village.org> To: Tim Vanderhoek Subject: Re: Docs for bsd.ports.mk Cc: John Fieber , ports@FreeBSD.ORG In-reply-to: Your message of "Sun, 18 Jan 1998 22:55:52 EST." References: Date: Sun, 18 Jan 1998 21:05:12 -0700 From: Warner Losh Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Tim Vanderhoek writes: : That said, once you've studied bsd.port.mk for a while, the whole : ports system takes on a new level of sex appeal, and we wouldn't : want to discourage new users from realizing that potential. ;-) Looking at bsd.port.mk does something for me, but that's not exactly how I'd describe what it does for me :-) Warner