From owner-freebsd-questions@FreeBSD.ORG Wed Jan 14 20:30:48 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C54D16A4CE for ; Wed, 14 Jan 2004 20:30:48 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19B9843D77 for ; Wed, 14 Jan 2004 20:30:43 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 8DAE32EC; Wed, 14 Jan 2004 22:30:42 -0600 (CST) Date: Wed, 14 Jan 2004 22:30:42 -0600 From: Tillman Hodgson To: freebsd-questions Message-ID: <20040115043042.GK415@seekingfire.com> References: <1074139882.5205.28.camel@closetotheedge> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1074139882.5205.28.camel@closetotheedge> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers User-Agent: Mutt/1.5.5.1i Subject: Re: How do YOU stay up to date? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2004 04:30:48 -0000 On Wed, Jan 14, 2004 at 11:11:22PM -0500, Duane Winner wrote: > I now understand how to use cvsup to keep my src and ports tree current. > I know how to use pkg_add -r to install new sotware, or go into > /usr/ports/whatever to make install. I know how to do portupgrade to > upgrade my installed ports, how to pkg_version -v to see what's out of > date with my tree, and how to cronjob cvsup to keep my trees current. (I > still need to play more with make world and whatnot) I think you've got the right tools, you jsut need to use them in different ways. > One thing that concerns me, at least on the laptops, is the amount of > time spent compiling new software as it is release, seeing as how we > will be running x, gnome and Yahweh knows what else.... You have enough machines to justify using a build host: a single machine that simply builds ports into packages (or compiles buildworld and buildkernel into the /usr/obj directory). You can then do binary installs off of the build host via NFS. It's a very handy architecture because it allows you to do offload the work of building to a separate server and roll out to other machines when it's convenient. It also helps ensure that other machines stay uniform and allows new machines to rolled out with little effort. -T -- "The most exhausting thing in life is being insincere." - Anne Morrow Lindbergh {American Author}