From owner-freebsd-questions@freebsd.org Mon Dec 4 10:37:40 2017 Return-Path: Delivered-To: freebsd-questions@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 3E920DF7A3E for ; Mon, 4 Dec 2017 10:37:40 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 02C90293D for ; Mon, 4 Dec 2017 10:37:39 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from leaf.local (unknown [88.202.132.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id 45FBF16E3 for ; Mon, 4 Dec 2017 10:37:36 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none (p=none dis=none) header.from=FreeBSD.org Subject: Re: Create list of ports to update To: freebsd-questions@freebsd.org References: From: Matthew Seaman Message-ID: <1293daad-1284-0eab-009a-6a6d3ba7373a@FreeBSD.org> Date: Mon, 4 Dec 2017 10:37:35 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2017 10:37:40 -0000 On 03/12/2017 16:40, Carmel NY wrote: > Reading up on "poudriere", it appears that I have to feed it a list of ports > that need to be updated. Unlike "synth" which can figure that out by itself, > it does seem counterproductive. > > My question, now that "portmaster" is apparently dead in the water, what is > the easiest way to construct a list of ports that need updating in the: > "port-category/port-name" format? With poudriere, what you're doing is populating a repository. You tell poudriere what ports you want available, and it will build packages for each of them, plus all their dependencies and then create a repository from all those packages. Then later on you can update by running 'poudriere bulk' and it will work out what has been updated since the last time, and rebuild only those packages. To create a list of packages to feed into poudriere, try: % pkg query -e '%a == 0' %o That gives you a list of all the packages you installed directly, omitting anything installed just as a dependency. All the dependencies will be built automatically and available in your repo; not listing them explicitly in the list passed to poudriere is a small optimization that helps avoid some occasional errors when packages get removed or renamed. Cheers, Matthew