From owner-freebsd-ports  Fri Aug  2 07:56:08 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA11767
          for ports-outgoing; Fri, 2 Aug 1996 07:56:08 -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 HAA11761
          for <ports@freebsd.org>; Fri, 2 Aug 1996 07:56: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 HAA19558; Fri, 2 Aug 1996 07:54:17 -0700 (PDT)
To: Mark Murray <mark@grondar.za>
cc: ports@freebsd.org
Subject: Re: Automatic ports Makefile generator? 
In-reply-to: Your message of "Fri, 02 Aug 1996 16:27:07 +0200."
             <199608021427.QAA15279@grumble.grondar.za> 
Date: Fri, 02 Aug 1996 07:54:17 -0700
Message-ID: <19556.838997657@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> grumble $ makeport
> Makeport - 0.1-ALPHA
> what is the name of your port? hello-1.3
> directory hello-1.3 found OK
> file hello-1.3.tar.gz found OK
> untarrring hello-1.3.tar.gz............OK
> creating diff.....OK
> removing original sources.
> 
> Q&A Time!
> 
> Does your port need GNU make? n
> Does your port need imake? n
> Does your port have its own "configure" script? y
> ...

That sounds pretty reasonable, though again I'd caution you against
making `makeport' a monolithic utility which "knows" which questions
to ask and rather design it as a fairly intelligent "ports variable
description file" and a library of functions for dealing with it.
Then you can write this Q&A sequence as a series of questions, as you
show above, or you can later migrate to some much fancier Tk based
thingie.

					Jordan