From owner-freebsd-ports@FreeBSD.ORG Thu Jan 22 20:23:42 2015 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21ECC223; Thu, 22 Jan 2015 20:23:42 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B05D7EF3; Thu, 22 Jan 2015 20:23:41 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t0MKOM81093195; Thu, 22 Jan 2015 12:24:22 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: ports@FreeBSD.org, Baptiste Daroussin In-Reply-To: <20150122180912.GE81001@ivaldir.etoilebsd.net> References: <20150122180912.GE81001@ivaldir.etoilebsd.net> From: "Chris H" Subject: Re: [HEADSUP] Upcoming change in dependency registration Date: Thu, 22 Jan 2015 12:24:22 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <7996d75b9d724f65af7dd3f63033eb03@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 20:23:42 -0000 On Thu, 22 Jan 2015 19:09:13 +0100 Baptiste Daroussin wrote > Hi all > > Some changes are coming to the ports, the diff is rather simple, but the > change of behaviour is worse notifying all maintainers: > > Currently and since very long the dependency registration in the ports tree > is based on the origin of the packages. which makes it unfriendly with > FLAVORS and Subpackages. > > The ports tree has been changed in the branch > https://svnweb.freebsd.org/ports/projects/rework-dependency-registration/ > > so now it basically do the same kind of mechanism which is done during the .. > > Last side effect it also prepare the way to be able to depend on provides and > depend correctly on "smart dep" aka "perl5>=5.18.2_3<5.20" > > This change is being exp-run and will be committed as soon as it is stable > enough > > Best regards, > Bapt Hi Bapt. Will this be OR'ed? In other words; will this create compatibility issues for anyone using ports without this change? While I develop on 11-CURRENT. I wonder about developers that aren't, or haven't yet incorporated this new change? (granted, developers *should* always be running *fairly* current revision(s)). I guess I'm just wondering if ports, and those still using them, that don't *yet* incorporate this change, will still continue to work as intended/expected (at least for awhile). I'm still reading the proposed changes. :) Thanks. --Chris