From owner-freebsd-ports@FreeBSD.ORG Sun Feb 14 22:20:13 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 729A31065670 for ; Sun, 14 Feb 2010 22:20:13 +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 4AB668FC08 for ; Sun, 14 Feb 2010 22:20:13 +0000 (UTC) Received: from vivi.cat.pdx.edu (vivi.cat.pdx.edu [131.252.214.6]) by epona.bluerosetech.com (Postfix) with ESMTPSA id 664735C01B; Sun, 14 Feb 2010 14:20:12 -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 9AEA824D89; Sun, 14 Feb 2010 14:20:10 -0800 (PST) Message-ID: <4B787718.3040605@bitfreak.org> Date: Sun, 14 Feb 2010 14:20:08 -0800 From: Darren Pilgrim User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Garrett Cooper References: <4B776D6F.10008@bitfreak.org> <20100214180243.GA79050@atarininja.org> <4B7863FE.9040108@bitfreak.org> <7d6fde3d1002141348q1facadd4l5b11b4749379d49f@mail.gmail.com> In-Reply-To: <7d6fde3d1002141348q1facadd4l5b11b4749379d49f@mail.gmail.com> 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 22:20:13 -0000 Garrett Cooper wrote: > Vendor provided binaries are a fun ball of wax to deal with > because you need to have all dependencies come from the same generic > pool as the package [/ port] itself, as any > This sounds trivial, but it requires changes to pkg_add (for > fetching / installing a particular revision of the code, as well as > `slotting' the packages themselves), determining elf-version, ld > modifications, as well as a few other things. It's been implemented at > my work [Ironport] from what I've been told, but 1) I'm not sure how > complete it is, 2) I'm not sure how tested it is, and 3) it hasn't > been reviewed yet and I'm not sure how much would be put back in the > community at large to be honest... Or you can take the vendor's approach and make a static binary with all the dependencies (i.e., libraries) compiled in.