From owner-freebsd-ports  Fri Aug  2 05:13:11 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id FAA04659
          for ports-outgoing; Fri, 2 Aug 1996 05:13:11 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA04653
          for <FreeBSD-Ports@freebsd.org>; Fri, 2 Aug 1996 05:13:05 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id FAA19232; Fri, 2 Aug 1996 05:11:50 -0700 (PDT)
To: Chuck Robey <chuckr@glue.umd.edu>
cc: "David E. O'Brien" <obrien@Nuxi.cs.ucdavis.edu>,
        FreeBSD Ports <FreeBSD-Ports@freebsd.org>
Subject: Re: Sample Makefile 
In-reply-to: Your message of "Fri, 02 Aug 1996 07:50:00 EDT."
             <Pine.OSF.3.95.960802074357.5610C-100000@skipper.eng.umd.edu> 
Date: Fri, 02 Aug 1996 05:11:50 -0700
Message-ID: <19230.838987910@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> That's what you were heading towards, a Makefile that had a spot for
> everything, and could be filled in using a point/click tool, right?  Or
> did I misread you?

That's basically it, though data driven so that you could update your
template easily whenever you added new variables and such.  I think
the only way of really proving the efficacy of this design would be to
implement a proof-of-concept..

					Jordan