From owner-freebsd-ports@freebsd.org Tue May 4 15:59:33 2021 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B1FC96374CF for ; Tue, 4 May 2021 15:59:33 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FZPfs1zrDz3j11 for ; Tue, 4 May 2021 15:59:32 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 144FxYNa005982; Tue, 4 May 2021 08:59:40 -0700 (PDT) (envelope-from portmaster@bsdforge.com) MIME-Version: 1.0 Date: Tue, 04 May 2021 08:59:34 -0700 From: Chris To: "@lbutlr" Cc: FreeBSD Subject: Re: Ports recompile for 13.0-RELEASE In-Reply-To: References: User-Agent: UDNSMS/17.0 Message-ID: X-Sender: portmaster@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4FZPfs1zrDz3j11 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2021 15:59:33 -0000 On 2021-05-04 07:10, @lbutlr wrote: > With the move to FreeBSD 13.0 is there a simple (single step) way to > reinstall all > the current ports other than saving off a list of the ports and then > stepping > through that list to reinstall them? It was very inefficient when moving to > 12.0 > as many ports in the list, of course, were dependent on other ports, but > then got > recompiled, sometimes multiple times. I know I ended up in a make loop where > came > was compiled over and over again until I aborted, listed the current ports, > differ > on the previous ports, and picked a port I though would have a lot of reps > to > restart the compile. I then did this several more times to get back to where > I had > been on 11.x > > And there's still no way to tell if a port was installed from pkg or from > ports, > correct? Since I use MariaDB instead of MySQLI have to be sure I don't try > to use > package for anything that will try to install MySQL instead. > > And finally, the release of 13.0 ends the 12.x versions, right? There will > not be a 12.3. > > (And yes, I've tried moving to poudrerie several times and we do not get on. > At all.) Not a big fan of poudrerie. If I must, I generally choose synth. But try to avoid both if at all possible. jail(8) is my go-to for most things they try to facilitate. While this isn't the simple "set it, and forget it" solution you seek. I find that picking a meta-port/package as part of something I'm installing, gets me pretty close to all I need. The key to my method is the "recursive" keyword. IOW # cd /usr/ports/x11/xorg/ # make config-recursive (repeat this until dialog stops appearing) When complete # make package-recursive (install) clean If I'm in my build jail and have a /usr/ports/packages/(All|latest) I (ultimately) end up with a nice package repo that facilitates an image install or upgrade path from a fresh install. HTH --Chris