From owner-freebsd-ports@freebsd.org Sat Jan 28 17:17:56 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E71CCC47B0 for ; Sat, 28 Jan 2017 17:17:56 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 258661021 for ; Sat, 28 Jan 2017 17:17:55 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1D47020658 for ; Sat, 28 Jan 2017 12:17:55 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Sat, 28 Jan 2017 12:17:55 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=dwJBhnwkhSiQnQsdaxwjDaFULs0=; b=G4f9Hs mLoBF3sLhoj+SHTFGve13q/08gNmgMW7IIVceB/sfjOC7xlBRtGp3VuApJA27FLS UXCQCKIGwNpZq6NcHh36Ov7nFJXcTCvUF46qznIquGkNkZpB1vuyE3X9xHyCUsHn AqGUdGUQWbzQpNSb0yYLbEqpfxLx4fHeK0ztg= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=smtpout; bh=dwJBhnwkhSiQnQ sdaxwjDaFULs0=; b=OUcmnDRhQjxSU/+Py4ZQ1g+rQrFRHpGaHnGQd/Mdztr1rC /xzRbJ3h2IPH1v5BUe4rve4PusGgQxOh5YMLEQ2aUkGUA6UcCi4a/V2r3Fh7ZO2/ pa3Tpw4PRr6hcsbl+inO8ZWrzRjRIp+avd3rzKdg8joK2Rnnvj/ow++id8SHE= X-ME-Sender: X-Sasl-enc: 6+jekwMHbRgurVAXSfjUdvTMJ31UR8kA7iisq7Et0mYN 1485623874 Received: from pumpkin.growveg.org (pumpkin.growveg.org [82.70.91.101]) by mail.messagingengine.com (Postfix) with ESMTPA id B59307E2DA for ; Sat, 28 Jan 2017 12:17:54 -0500 (EST) To: freebsd-ports@freebsd.org From: tech-lists Subject: a quick question about make package-recursive Message-ID: Date: Sat, 28 Jan 2017 17:17:53 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Jan 2017 17:17:56 -0000 Hello ports@, Is make package-recursive smart enough to detect when: 1. there is already a package in /usr/ports/packages (so that it doesn't re-make a package for an installed port) 2. a port is installed but there is no package (so that it just installs the package into /usr/ports/packages) Let's say I'm in /usr/ports/mail/mutt. There are some (but not all) build dependencies installed, and some (but not all) run dependencies installed. All of these have packages built, and I'm not running make clean. Assume I'm not changing anything with make configure or configure-recursive. If I type make package-recursive in /usr/ports/mail/mutt, is it going to re-make the packages for all the stuff already installed? For context, this is on aarch64. I don't want it to spend time recompiling packages it already has. What I'm doing at the moment is keeping an eye on build and run dependencies, and going into each one and typing make package, so that at some time in the future, if I have to reinstall from scratch, I can point pkg at the packages I've already made. Basically I want to know if there's a smarter way of doing this. I *think* I saw a ports dependencies being written a new package despite the package already being there. thanks, -- J.