From owner-freebsd-stable Tue Aug 29 18: 8:23 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sf-gw.envolved.com (w018.z064220173.sjc-ca.dsl.cnc.net [64.220.173.18]) by hub.freebsd.org (Postfix) with ESMTP id 17B4C37B423 for ; Tue, 29 Aug 2000 18:08:22 -0700 (PDT) Received: from envolved.com (IDENT:sbeitzel@[192.168.0.51]) by sf-gw.envolved.com (8.9.3/8.9.3) with ESMTP id SAA14703; Tue, 29 Aug 2000 18:05:46 -0700 (PDT) (envelope-from sbeitzel@envolved.com) Message-Id: <200008300105.SAA14703@sf-gw.envolved.com> Date: Tue, 29 Aug 2000 18:05:39 -0700 (PDT) From: Stephen Beitzel Reply-To: Stephen Beitzel Subject: Re: Most stable stable? (or..why use -R?) And...keeping ports upto date? To: keen@damoe.wireless-isp.net Cc: stable@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29 Aug, David Raistrick wrote: > What would be the correct proceedure to remain uptodate (or just to > manually update them occasionally) with the entire ports collection? I don't know about the most stable STABLE, but the ports question is pretty easy. Create a supfile (go ahead and base it off /usr/src/share/examples/cvsup/ports-supfile) and add a job to /etc/crontab to cvsup the ports tree periodically. If you don't want to mess with crontab, you could write a shell script that just executes 'cvsup -g -L 2 file_name' and put it in /etc/periodic/[daily|weekly|monthly] Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message