From owner-freebsd-ports Wed Jan 9 2:12:20 2002 Delivered-To: freebsd-ports@freebsd.org Received: from fling.sanbi.ac.za (fling.sanbi.ac.za [196.38.142.119]) by hub.freebsd.org (Postfix) with ESMTP id 3EF8137B400 for ; Wed, 9 Jan 2002 02:12:15 -0800 (PST) Received: from johann by fling.sanbi.ac.za with local (Exim 3.13 #4) id 16OFgW-00019W-00; Wed, 09 Jan 2002 12:10:16 +0200 Date: Wed, 9 Jan 2002 12:10:16 +0200 From: Johann Visagie To: Tony Maher Cc: admin@govital.net, ports@FreeBSD.ORG Subject: Re: FreeBSD Port: portupgrade-20020103 Message-ID: <20020109101016.GD2775@fling.sanbi.ac.za> References: <3C3A9C41.C16CF8BA@govital.net> <200201080906.g08968p80613@yellow.biolateral.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200201080906.g08968p80613@yellow.biolateral.com.au> User-Agent: Mutt/1.3.25i 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 Tony Maher on 2002-01-08 (Tue) at 20:06:08 +1100: > > > 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: > [ snip ] > > But it would be nice if the ports system handled it intrinsically. What about the idea of a standard target for ports ("help"?) that simply lists all the options which may be used when building that port? -- V To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message