From owner-freebsd-ports Mon Sep 25 2:53:39 2000 Delivered-To: freebsd-ports@freebsd.org Received: from puck.firepipe.net (mcut-b-167.resnet.purdue.edu [128.211.209.167]) by hub.freebsd.org (Postfix) with ESMTP id 7B5FE37B42C for ; Mon, 25 Sep 2000 02:53:37 -0700 (PDT) Received: by puck.firepipe.net (Postfix, from userid 1000) id 529D018E4; Mon, 25 Sep 2000 04:53:41 -0500 (EST) Date: Mon, 25 Sep 2000 04:53:41 -0500 From: Will Andrews To: Neil Blakey-Milner Cc: FreeBSD Ports Subject: Re: makeport part deux - automated port creation tools. Message-ID: <20000925045341.N1054@puck.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Neil Blakey-Milner , FreeBSD Ports References: <20000924034526.A46867@mithrandr.moria.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20000924034526.A46867@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Sun, Sep 24, 2000 at 03:45:26AM +0200 X-Operating-System: FreeBSD 4.1-STABLE i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Sep 24, 2000 at 03:45:26AM +0200, Neil Blakey-Milner wrote: > Anyway, I've only just got back to hacking on these. makeport.pl also > attempted USE_GMAKE if 'make' failed in a specific way, and searched for > ALL_TARGET, if it wasn't 'all'. Anyway, I'd love some comments. How about committing these to a port? ports/devel/makeport? If they're in the repository that might give you a little more reason to maintain them. Plus, have you considered using templates to do certain things? Maybe adding a utility to the makeport script to generate PLISTs (nahh.. that ought to go in bsd.port.mk and called from makeport)? Blah.. /me goes to sleep. -- Will Andrews GCS/E/S @d- s+:+ a--- C++ UB++++$ P+ L- E--- W+ N-- !o ?K w--- O- M+ V- PS+ PE++ Y+ PGP+>+++ t++ 5 X+ R+ tv+ b++ DI+++ D+ G++ e>++++ h! r- y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message