From owner-freebsd-questions@FreeBSD.ORG Sun Oct 7 21:09:46 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A3D21106566B for ; Sun, 7 Oct 2012 21:09:46 +0000 (UTC) (envelope-from rfg@tristatelogic.com) Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 81C078FC08 for ; Sun, 7 Oct 2012 21:09:46 +0000 (UTC) Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1]) by segfault.tristatelogic.com (Postfix) with ESMTP id ACCAF5081F for ; Sun, 7 Oct 2012 14:09:44 -0700 (PDT) To: freebsd-questions@freebsd.org Date: Sun, 07 Oct 2012 14:09:44 -0700 Message-ID: <14763.1349644184@tristatelogic.com> From: "Ronald F. Guilmette" Subject: Building Ports: Is there a "make" equivalent for --batch ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Oct 2012 21:09:46 -0000 I am impatient by nature. Nowadays, whenever I use portinstall/portupgrade, I use the --batch option, so that I don't have to sit around at the console, waiting for and then accepting the default build options for a boatload of depended-upon ports for whatever I am actually trying to install or upgrade. However there's one instance where I don't know how to get this functionality, i.e. the functionality provided by the --batch option. On this page: http://cnsnap.cn.freebsd.org/doc/en/books/handbook/ports-using.html in Section 4.5.4.2, a user who is just installing a new system is instructed to do the following: # cd /usr/ports/ports-mgmt/portupgrade # make install clean (You have to do this in order to get portinstall/portupgrade installed. These tools can then be used to build & install other ports.) The problem is that these days, portupgrade itself is, apparently, dependent upon a whole slew of other ports. So while building portupgrade itself it appears that there is currently no escape from having to sit at the console and accept a whole bunch of default options for the whole bunch of other ports upon which portupgrade itself depends. Or is there?