From owner-cvs-ports  Tue Jul 30 15:42:52 1996
Return-Path: owner-cvs-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA14578
          for cvs-ports-outgoing; Tue, 30 Jul 1996 15:42:52 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA14560;
          Tue, 30 Jul 1996 15:42:33 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id PAA12914; Tue, 30 Jul 1996 15:42:25 -0700 (PDT)
Date: Tue, 30 Jul 1996 15:42:25 -0700 (PDT)
Message-Id: <199607302242.PAA12914@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org,
        cvs-ports@freefall.freebsd.org
In-reply-to: <481.838765345@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: cvs commit: ports/devel/tkcvs Makefile
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-cvs-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * Cool, a sample Makefile.  I still like the idea of making this a more
 * *useful* sample Makefile, however, by sticking it into a template
 * port.  What's wrong with more front-line documentation in the ports
 * tree?

I think such a "template" port won't be very useful without the
handbook anyway.  For you or me, the sample Makefile is probably all
that's needed to keep the ports in order (little pun intended) but not
so for part-time porters....

Satoshi