Date: Mon, 22 Dec 2025 10:30:35 -0800 From: Mark Millard <marklmi@yahoo.com> To: void <void@f-m.fm> Cc: freebsd-x11@freebsd.org, freebsd-pkg@freebsd.org Subject: Re: qt6-only in poudriere. Is it possible? Message-ID: <CF33BA2B-B611-4319-B2F1-A051C1F5D756@yahoo.com> In-Reply-To: <aUlVn57Zqw4ZFRBe@int21h> References: <aUlVn57Zqw4ZFRBe@int21h>
index | next in thread | previous in thread | raw e-mail
On Dec 22, 2025, at 06:28, void <void@f-m.fm> wrote:
> Is there a way (yet) to have qt6- *only* for qt- flavoured ports?
> If there is a qt5-flavour, I don't want it built at all. I'm using poudriere. Am building on 15-stable and -current.
[You are not specific if you are doing "bulk -a" style
builds vs. being more selective about what is built.]
A partial answer, just for preventing qt5 use (but
not for forcing qt6 use instead) is . . .
poudriere(-devel) has support for having various *make.conf
files:
Create optional make.conf
You can also specify a global make.conf which will be used for all the
jails. Any of the following are allowed and will all be used in the
order shown:
/usr/local/etc/poudriere.d/make.conf
/usr/local/etc/poudriere.d/<setname>-make.conf
/usr/local/etc/poudriere.d/<tree>-make.conf
/usr/local/etc/poudriere.d/<jailname>-make.conf
/usr/local/etc/poudriere.d/<tree>-<setname>-make.conf
/usr/local/etc/poudriere.d/<jailname>-<tree>-make.conf
/usr/local/etc/poudriere.d/<jailname>-<setname>-make.conf
/usr/local/etc/poudriere.d/<jailname>-<tree>-<setname>-make.conf
/usr/local/etc/poudriere.d/hooks/plugins/<plugin>/make.conf
In such a file that would be used for builds where you
want this status, prevent all devel/qt5* from building
via:
.if ${.CURDIR:M*/devel/qt5*}
IGNORE= I do not want qt5 built (so it will not be used)
.endif
Nothing dependent on any of those will end up built.
Even if your intent includes use of qt6 instead, this
much could be done now and left in place. You would
also learn what all ends up not present that you want a
qt6 variant of.
For reference for what would directly not be built based
on the above:
# ls -dC1 /usr/ports/devel/qt5*/
/usr/ports/devel/qt5-assistant/
/usr/ports/devel/qt5-buildtools/
/usr/ports/devel/qt5-concurrent/
/usr/ports/devel/qt5-core/
/usr/ports/devel/qt5-dbus/
/usr/ports/devel/qt5-designer/
/usr/ports/devel/qt5-help/
/usr/ports/devel/qt5-linguist/
/usr/ports/devel/qt5-linguisttools/
/usr/ports/devel/qt5-location/
/usr/ports/devel/qt5-qdbus/
/usr/ports/devel/qt5-qdbusviewer/
/usr/ports/devel/qt5-qdoc-data/
/usr/ports/devel/qt5-qdoc/
/usr/ports/devel/qt5-qmake/
/usr/ports/devel/qt5-remoteobjects/
/usr/ports/devel/qt5-script/
/usr/ports/devel/qt5-scripttools/
/usr/ports/devel/qt5-scxml/
/usr/ports/devel/qt5-testlib/
/usr/ports/devel/qt5-uitools/
/usr/ports/devel/qt5/
[I'll note that freebsd-pkg is probably not the right
list for how-to-build questions (instead of questions
and issues specifically tied to using the pkg and
pkg-static commands).]
[My reply may not reach the freebsd-x11 list.]
===
Mark Millard
marklmi at yahoo.com
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CF33BA2B-B611-4319-B2F1-A051C1F5D756>