From owner-freebsd-ports@freebsd.org Thu Nov 30 16:09:15 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44F9CE5F907 for ; Thu, 30 Nov 2017 16:09:15 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 27C4A6A57F; Thu, 30 Nov 2017 16:09:15 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id 77B0BB5E2; Thu, 30 Nov 2017 16:09:14 +0000 (UTC) From: Jan Beich To: Mathieu Arnold Cc: freebsd-ports@freebsd.org Subject: Re: [HEADSUP] Flavors, and specifically, Python flavors landing today References: <7c9a5e55-505f-9160-2886-56c451cdf9b1@FreeBSD.org> Date: Thu, 30 Nov 2017 17:09:08 +0100 In-Reply-To: <7c9a5e55-505f-9160-2886-56c451cdf9b1@FreeBSD.org> (Mathieu Arnold's message of "Thu, 30 Nov 2017 16:32:44 +0100") Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Nov 2017 16:09:15 -0000 Mathieu Arnold 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.