From owner-freebsd-ports@FreeBSD.ORG Sun Jun 3 22:52:09 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16F12106567B for ; Sun, 3 Jun 2012 22:52:09 +0000 (UTC) (envelope-from rflynn@acsalaska.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id D8DE68FC0A for ; Sun, 3 Jun 2012 22:52:08 +0000 (UTC) Received: from [127.0.0.1] (squeeze.lan.rachie.is-a-geek.net [192.168.2.30]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id C6AB27E853 for ; Sun, 3 Jun 2012 14:52:06 -0800 (AKDT) Message-ID: <4FCBEA95.6050807@acsalaska.net> Date: Mon, 04 Jun 2012 00:52:05 +0200 From: Mel Flynn User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <20120603192023.GA8350@slackbox.erewhon.net> <20120603200101.GB98939@ithaqua.etoilebsd.net> <20120603215406.GC98939@ithaqua.etoilebsd.net> <4FCBE328.3030702@FreeBSD.org> In-Reply-To: <4FCBE328.3030702@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: optionsng ignores /var/db/ports//options X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2012 22:52:09 -0000 On 4-6-2012 0:20, Michael Scheidell wrote: > optionsng should have been 100% upward compatible. you should not be > forced to an an emergency update of a port you maintain just because the > ports tree broke things. This has always been broken. It's just exposed by Roland cause he's /adding/ an option and never had any. graphics/py-yaml has the work around and it's been there since version 1.14: (line 25) The real issue is that something created for slave ports (thus set before any of the option framework comes in play) is "abused" by Mk/ frameworks that only come in sight /after/ options.mk. This causes two versions of UNIQUENAME in the execution stream to exist. One before the framework is included and one after. -- Mel