Date: Mon, 6 Dec 2021 11:33:31 -0800 From: Dave Hayes <dave@jetcafe.org> To: questions@freebsd.org Subject: Re: poudriere options Message-ID: <20211206113331.615be42f@bigus.dream-tech.com> In-Reply-To: <0bc4b4f5-93c2-4f7e-805c-5aa0efc9538f@www.fastmail.com> References: <Ya4N46eihoPZIvEy@io.chezmoi.fr> <9c25f179-c051-20ef-5e6c-fda9673e9a2f@langille.org> <Ya4mrSv1XkifwRSC@io.chezmoi.fr> <D5708C71-F31E-4AFA-869C-5F05304BD557@darktemple.ch> <3d0ab685-bb39-47c9-ab7d-63250e5b1746@www.fastmail.com> <9D13B32D-0EDD-4F1A-8E09-83E8D681B98D@darktemple.ch> <0bc4b4f5-93c2-4f7e-805c-5aa0efc9538f@www.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 06 Dec 2021 12:33:41 -0500 "Dan Langille" <dan@langille.org> wrote: > You can put them all in /usr/local/etc/poudriere.d/make.conf So this is just another take on this idea. I tend to use poudriere's options directory mechanism (e.g. /usr/local/etc/poudriere.d/options) for this kind of thing. Three reasons to prefer this: 1) It's less confusing and reserves make.conf for global ideas like DEFAULT_VERSIONS. 2) Port specific options can change (e.g. when moving to new ports quarterly) 3) Git works wonders in this context, since you can just make your changes with 'poudriere options' and then commit the result. This allows tracking of what options have changed. -- Dave Hayes - Consultant - LA CA, USA - dave@dream-tech.com >>>> *The opinions expressed above are entirely my own* <<<< Faith (n): The quality by which we believe what we would otherwise think was false.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20211206113331.615be42f>