From owner-freebsd-ports Tue Jan 8 1: 6:36 2002 Delivered-To: freebsd-ports@freebsd.org Received: from yellow.biolateral.com.au (c31516.thorn1.nsw.optusnet.com.au [203.164.22.4]) by hub.freebsd.org (Postfix) with ESMTP id DE57637B416 for ; Tue, 8 Jan 2002 01:06:28 -0800 (PST) Received: (from tonym@localhost) by yellow.biolateral.com.au (8.11.6/8.11.6) id g08968p80613; Tue, 8 Jan 2002 20:06:08 +1100 (EST) (envelope-from tonym) Date: Tue, 8 Jan 2002 20:06:08 +1100 (EST) From: Tony Maher Message-Id: <200201080906.g08968p80613@yellow.biolateral.com.au> To: admin@govital.net Cc: ports@FreeBSD.ORG Subject: Re: FreeBSD Port: portupgrade-20020103 In-Reply-To: <3C3A9C41.C16CF8BA@govital.net> Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > while, ever since I started using the portupgrade program. It would be > nice if the ports sub system would remember what command line options > were used when a port has been built. Or maybe having the option of For portupgrade it already exists: /usr/local/etc/pkgtools.conf MAKE_ARGS = { 'databases/mysql*-*' => 'DB_DIR=/db/mysql SKIP_INSTALL_DB=yes', 'print/ghostscript-afpl*-*' => '-DA4', } But it would be nice if the ports system handled it intrinsically. -- tonym To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message