From owner-freebsd-stable Wed Feb 21 2:52:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.venon.com (ns1.venon.com [64.7.7.83]) by hub.freebsd.org (Postfix) with ESMTP id 17AA837B401 for ; Wed, 21 Feb 2001 02:52:42 -0800 (PST) (envelope-from all@biosys.net) Received: from megalomaniac.biosys.net (megalomaniac.venon.com [64.7.7.82]) by ns1.venon.com (Postfix) with ESMTP id DFC31D14BC; Wed, 21 Feb 2001 05:51:01 -0500 (EST) Message-Id: <4.3.2.7.2.20010221054413.00c443a0@64.7.7.83> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 21 Feb 2001 05:51:36 -0500 To: Mark Drayton , freebsd-stable@FreeBSD.ORG From: Allen Landsidel Subject: Re: cvsup confusion In-Reply-To: <20010221104227.A8439@tethys.valhalla.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:42 2/21/2001 +0000, Mark Drayton wrote: >What sort of logging should I expect from cvsup -g -L 2? I get 'added >delta' etc for the ports, but only 'Updating collection src-all/cvs' for >stable. Is this correct? I'd like a list of changed files each time I >cvsup. Haven't looked at that myself, but I'm sure there is a way.. I get the same results with -L 2 however.. The difference here is that in the ports collection, it's downloading patches and diffs to the pre-packaged ports distributions, which come from 3rd parties a lot of the time. The src-all collection is created and maintained by the project however, so (I think) it's more likely that you're just downloading the updated files, and not downloading diffs of existing files. If the files in cvs are more recent than those on your system, yours are replaced instead of patched. If there is no easy way to do this with cvsup, then you could just get a directory list to a file before and after you cvsup, and then diff the files. >As a matter of interest, how does everyone else run cvsup from cron? I'm >using: Two things differently from what you're doing.. First, I put all my cvsup commands in one file, so I don't need to run it multiple times on different scripts.. Second, I don't mess with cron.. why clutter up your crontab when you have /etc/periodic/* at your disposal? I just stick a script in /etc/periodic/weekly and it does the cvsup, then a success-dependant buildworld, installworld, buildkernel, and installkernel in that order. If all goes according to plan, then it reboots.. I intervene if something comes across the list stating that something is broken, of course. ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message