Date: Sat, 29 May 2004 18:17:21 -0400 From: Brian Reichert <reichert@numachi.com> To: Peter Schuller <peter.schuller@infidyne.com> Cc: freebsd-ports@freebsd.org Subject: Re: Maintaing a seprate build machine for ports Message-ID: <20040529221721.GN34662@numachi.com> In-Reply-To: <200405291952.45555.peter.schuller@infidyne.com> References: <200405291952.45555.peter.schuller@infidyne.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 29, 2004 at 07:52:45PM +0200, Peter Schuller wrote: > What I plan on doing is using 'make package-recursive' on all wanted ports, > followed by a 'portupgrade -arPP' on the live machine. Unfortunately this has > some issues. In particular I will loose the ability to use pkgtools.conf to > maintain per-package compilation options automatically, and I believe it will > be difficult to make sure exactly the right ports are built because of the > non-obvious (sometimes) difference between installed package names and the > ports that built them. I use 'portupgrade -R --package' to make packages out of the ports that I want, and that does honor pkgtools.conf. Then I can use 'portupgrade -arPP' on my other machines. > So I have two questions: > > * I want to perform the builds separately from maintainng the used ports on > the machine used for the build. What is the distinction between 'perform the builds' and 'used ports'? > > -- > / Peter Schuller, InfiDyne Technologies HB -- Brian Reichert <reichert@numachi.com> 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040529221721.GN34662>