Date: Tue, 10 Jun 2003 09:25:06 -0400 From: Scott Lambert <lambert@lambertfam.org> To: freebsd-isp@freebsd.org Subject: Re: Updating Ports on Production Servers Message-ID: <20030610132506.GA90654@laptop.lambertfam.org> In-Reply-To: <20030609232644.U23396@znfgre.qbhto.arg> References: <8F69143C0B1A9F4D95AFC58CF69877E501354AB0@exhsto1.se.dataphone.com> <20030609232644.U23396@znfgre.qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 09, 2003 at 11:34:46PM -0700, Doug Barton wrote: > If you're installing stuff on production servers, you probably want to > build a package on a trusted system, then ship the package out to the > production servers and use pkg_add/pkg_delete. Building ports on > individual machines generally doesn't scale, and adding portupgrade to > that mix is destined to complicate things rather dramatically. I NFS mount my ports tree. Using the build "-p -P" options to portupgrade, you build the package once, for whichever machine, and the next machine that needs it just grabs it from ports/packages/. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030610132506.GA90654>