Date: Wed, 14 Mar 2001 02:36:07 +0200 (EET) From: Maxim Sobolev <sobomax@FreeBSD.org> To: obrien@FreeBSD.org Cc: sobomax@FreeBSD.org (Maxim Sobolev), cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/netinet ip_output.c Message-ID: <200103140036.f2E0a8v15357@vic.sabbo.net> In-Reply-To: <20010313162107.C86088@dragon.nuxi.com> from "David O'Brien" at Mar 13, 2001 04:21:07 PM
next in thread | previous in thread | raw e-mail | index | archive | help
> > On Wed, Mar 14, 2001 at 02:10:37AM +0200, Maxim Sobolev wrote: > > I believe he meant the situation when you have to deploy the same software > > on many machines. In this case you can do: > > master# cd /usr/ports/www/mozilla > > master# make package clean > > > > slave0# pkg_add /usr/ports/packages/www/mozilla-x.y.tgz > > slave1# pkg_add /usr/ports/packages/www/mozilla-x.y.tgz > > ... > > slaveN# pkg_add /usr/ports/packages/www/mozilla-x.y.tgz > > > > And save N * (time to compile huge mozilla) for something more productive. > > It is faster to download the pre-compiled binary package from > ftp*.freebsd.org than doing the `make package clean' step. Also saves > diskspace. So I don't see where the above is any better. It's better because: 1. People don't trust pre-compiled packages and like compiling by themselves. This also allows to use fancy optimisations like -O100 and -fvery-cool-but-expensive-optimisation. 2. In the case when small FreeBSD-specific bug found and fixed you will not have to re-download the whole thing. 3. It's usually a certain time lag between port update and package appearance at ftp*.freebsd.org. 4. You can compile packages for the several different releases, say -current for your notebook, -stable for a production machine 3-stable for your grandma etc. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200103140036.f2E0a8v15357>