From owner-freebsd-ports@freebsd.org Sun Dec 27 08:56:23 2020 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 E822D4B3BE9 for ; Sun, 27 Dec 2020 08:56:23 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D3ZKg6J6Gz3sn9; Sun, 27 Dec 2020 08:56:23 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (unknown [76.212.85.177]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: truckman) by smtp.freebsd.org (Postfix) with ESMTPSA id 54737AEB; Sun, 27 Dec 2020 08:56:23 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Date: Sun, 27 Dec 2020 00:56:21 -0800 (PST) From: Don Lewis Subject: Re: portmaster new development To: Kurt Jaeger cc: Thomas Mueller , freebsd-ports@freebsd.org In-Reply-To: Message-ID: References: <20201226124150.7c494410@dismail.de> <6d0d128b-9a75-34f4-830c-d8be05ded9cb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE 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: Sun, 27 Dec 2020 08:56:24 -0000 On 27 Dec, Kurt Jaeger wrote: > Hi! > >> How is poudriere in that regard? I never used poudriere, have been >> intimidated by not wanting to use zfs or dialog4ports, or such an >> elaborate setup just to update one or a few ports. > > poudriere is really, really useful. Because it delivers a complete, > consistent package repo of all the ports (with individual options). > And it does so repeatable, down to one or several seperate os versions > to build for or a specific point in time for the ports tree, > with some individual options etc. > >> I found that poudriere uses dialog4ports; I much prefer to save >> options in a file such as Gentoo Linux does with make.conf and >> (NetBSD) pkgsrc does with mk.conf . > > That works as well. I have a checkout of the ports tree, use > make config to define non-default port options. This stores the > selected OPTIONs in /var/db/ports/, and poudriere uses those options > just fine. I set the options in /usr/local/etc/poudriere.d/make.conf. It is easier to set options consistently across ports, for instance enabling CUPS globally, than with dialog4ports, while also allowing per-port option setting. It is also possible to have multiple option settings for different OS versions, arches, or option sets contained in different make.conf files.