From owner-freebsd-ports@FreeBSD.ORG Sun Feb 14 20:58:43 2010 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1ED21106566B for ; Sun, 14 Feb 2010 20:58:43 +0000 (UTC) (envelope-from freebsd@bitfreak.org) Received: from epona.bluerosetech.com (epona.bluerosetech.com [204.109.56.17]) by mx1.freebsd.org (Postfix) with ESMTP id D47938FC12 for ; Sun, 14 Feb 2010 20:58:42 +0000 (UTC) Received: from vivi.cat.pdx.edu (vivi.cat.pdx.edu [131.252.214.6]) by epona.bluerosetech.com (Postfix) with ESMTPSA id D0E825C01B; Sun, 14 Feb 2010 12:58:41 -0800 (PST) Received: from [127.0.0.1] (c-76-115-170-205.hsd1.wa.comcast.net [76.115.170.205]) by vivi.cat.pdx.edu (Postfix) with ESMTPSA id DA4F224D89; Sun, 14 Feb 2010 12:58:39 -0800 (PST) Message-ID: <4B7863FE.9040108@bitfreak.org> Date: Sun, 14 Feb 2010 12:58:38 -0800 From: Darren Pilgrim User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Wesley Shields References: <4B776D6F.10008@bitfreak.org> <20100214180243.GA79050@atarininja.org> In-Reply-To: <20100214180243.GA79050@atarininja.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: Installing a different PORTVERSION based on OSVERSION? 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, 14 Feb 2010 20:58:43 -0000 Wesley Shields wrote: > On Sat, Feb 13, 2010 at 07:26:39PM -0800, Darren Pilgrim wrote: >> I'm working on a revision to a port where the current version doesn't >> work on 8.0-R; however, an older version does. Rather than roll the >> entire port back to an older version, I'd like to have the newer version >> available to 7.x and older and the older version available to 8.x and >> newer. Is it appropriate to install different versions of a port based >> on ${OSVERSION}? If so, do I just set the necessary variables after >> including bsd.port.pre.mk? > > This seems like a bad idea to me. How much effort would it take to fix > the port on 8.x and newer? The port contains a static-linked binary from the vendor--not something I can patch. > The other option is to mark it broken on 8.x and newer. The port currently sets BROKEN if OSVERSION >= 800000.