Date: Wed, 16 Mar 2005 18:25:21 -0500 From: Forrest Aldrich <forrie@forrie.com> To: "Frank J. Laszlo" <laszlof@tvog.net> Cc: ports@freebsd.org Subject: Re: Using the ports dev structure for individual projects.... Message-ID: <4238C061.9030807@forrie.com> In-Reply-To: <4238BFC6.1080709@tvog.net> References: <42388092.5030102@forrie.com> <4238BFC6.1080709@tvog.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4238C061.9030807>