From owner-freebsd-ports@FreeBSD.ORG Wed Mar 16 23:25:29 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8442416A4CE for ; Wed, 16 Mar 2005 23:25:29 +0000 (GMT) Received: from forrie.com (forrie.ne.client2.attbi.com [24.147.45.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F1D243D46 for ; Wed, 16 Mar 2005 23:25:29 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [192.168.1.99] (i-99.forrie.net. [192.168.1.99]) (authenticated bits=0) by forrie.com with ESMTP id j2GNPMI8097094; Wed, 16 Mar 2005 18:25:23 -0500 (EST) (envelope-from forrie@forrie.com) Message-ID: <4238C061.9030807@forrie.com> Date: Wed, 16 Mar 2005 18:25:21 -0500 From: Forrest Aldrich User-Agent: Mozilla Thunderbird 1.0.1 (Windows/20050307) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Frank J. Laszlo" References: <42388092.5030102@forrie.com> <4238BFC6.1080709@tvog.net> In-Reply-To: <4238BFC6.1080709@tvog.net> X-Enigmail-Version: 0.90.1.1 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.3.0(snapshot 20010925) (forrie.ne.client2.attbi.com) X-MailScanner-LocalNet: Found to be clean cc: ports@freebsd.org Subject: Re: Using the ports dev structure for individual projects.... X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2005 23:25:29 -0000 Hi there, We're taking the angle of a top-level makefile right now - to call the individual builds to the ports we require, then an install, then a "make package" (possibly via direct pkg_create). This is for a project that requires some control over versioning - I wanted to exploit the development environment provided by the ports structure, and not have to reinvent the wheel, necessarily.... Thanks! Frank J. Laszlo wrote: > Forrest Aldrich wrote: > >> I've been asked to take a few select ports from /usr/ports and create >> a build environment. >> >> This presents a few technical issues, some of which can be dealt with >> by overriding certain variables like PORTSDIR, NOPORTDOCS, et al. >> >> The second problem is ports are updated with some frequency, and we >> need to keep a stateful build environment so that each dependency is >> there "as-is" during that build. >> >> I figure I could lessen the pain of hacking variables by simply >> snapshotting the /usr/ports struture, placing that into a separate >> directory and then modifying PORTSDIR and DISTDIR in the build process. >> >> So before I go too far here, I wonder if someone else has done this - >> perhaps some examples/tips/feedback would be appreciated. >> >> >> Thanks..... >> >> > > I'm not sure I 100% understand what you are trying to do here, But > maybe this will give you some more information. > > http://www.franksworld.org/localuser_portinstall.html > > Hope that help.s > > Kind Regards, > Frank Laszlo