Date: Thu, 24 Feb 2022 00:43:22 +0000
From: bugzilla-noreply@freebsd.org
To: ports-bugs@FreeBSD.org
Subject: [Bug 262162] ports infrastructure: provide USES_${ARCH}
Message-ID: <bug-262162-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262162 Bug ID: 262162 Summary: ports infrastructure: provide USES_${ARCH} Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: feature Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: fuz@fuz.su CC: koobs@FreeBSD.org It is currently very awkward to register USES that depend on architecture.= =20 This is a use case that pops up every once in a while (e.g. when a port requires a certain build tools only on some architectures). See e.g. bug #261247. This is because USES cannot be set after <bsd.port.pre.mk> is included, but including that is required to access the ARCH macro. A possible workaround is using a construct like USES+=3D${ARCH:Mamd64:S/amd64/something} but that's hard to read and quite ugly. As a solution, the ports infrastructure should provide a macro USES_${ARCH} that if set is added to USES, permitting the definition of architecture specific USES. For example, this could be achieved by placing USES+=3D${USES_${ARCH}} after the definition of ARCH and before evaluation of USES in bsd.port.mk. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262162-7788>