Date: Thu, 30 Nov 2017 17:09:08 +0100 From: Jan Beich <jbeich@FreeBSD.org> To: Mathieu Arnold <mat@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: [HEADSUP] Flavors, and specifically, Python flavors landing today Message-ID: <vahr-ycij-wny@FreeBSD.org> In-Reply-To: <7c9a5e55-505f-9160-2886-56c451cdf9b1@FreeBSD.org> (Mathieu Arnold's message of "Thu, 30 Nov 2017 16:32:44 %2B0100") References: <7c9a5e55-505f-9160-2886-56c451cdf9b1@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mathieu Arnold <mat@FreeBSD.org> writes:
> In all the ports with Python dependencies, the *_DEPENDS entries MUST end
> with the flavor so that the framework knows which to build/use. This is done
> by appending '@${PY_FLAVOR}' after the origin (or @${FLAVOR} if in a Python
> module with Python flavors, as the content will be the same). For example:
>
> RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
Are merges to 2017Q4 still allowed for py-* ports? I'm assuming ports/
committers can handle trivial merge conflicts.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vahr-ycij-wny>