Date: 11 Jun 2002 16:37:06 -0400 From: Dan Pelleg <daniel@pelleg.org> To: Michael Lucas <mwlucas@blackhelicopters.org> Cc: Pete French <pfrench@firstcallgroup.co.uk>, stijn@win.tue.nl, stable@FreeBSD.ORG Subject: Re: code freeze Message-ID: <u2su1o97dsd.fsf@gs166.sp.cs.cmu.edu> In-Reply-To: <20020611115648.A84741@blackhelicopters.org> References: <20020611165559.A34669@pcwin002.win.tue.nl> <E17HnRS-000MCX-00@mailhost.firstcallgroup.co.uk> <20020611115648.A84741@blackhelicopters.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Lucas <mwlucas@blackhelicopters.org> writes: > On Tue, Jun 11, 2002 at 04:20:18PM +0100, Pete French wrote: > > I'm sure theres probably a way to have a single /usr/ports NFS mounted and to > > be able to do a 'make install' onto several machines, but if so I havent > > found it... :-) > > Allow me to recommend "make package" instead of "make install" when in > the port directory. > > Compile it exactly the way you want, and build it as a package. Then > you can nfs-mount the package dir, and even have a shell script run > "pkg_add" on your new machines. > > All the advantages of packages, and none of the disadvantages. > I used to do that for a while, but I didn't find an adequate way to package the dependencies the "make" may encounter and build. Nowadays, I do a "portupgrade -NpR foo" on the build machine, and "portupgrade -NPP foo" on the clients. -- Dan Pelleg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?u2su1o97dsd.fsf>