From owner-freebsd-questions Fri Feb 14 12:33:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA29502 for questions-outgoing; Fri, 14 Feb 1997 12:33:52 -0800 (PST) Received: from terra.stack.nl (terra.stack.nl [131.155.140.128]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA29496 for ; Fri, 14 Feb 1997 12:33:45 -0800 (PST) Received: from xaa.stack.nl (uucp@localhost) by terra.stack.nl (8.8.5) with UUCP id VAA03228; Fri, 14 Feb 1997 21:33:07 +0100 (MET) Received: (from freebsd@localhost) by xaa.stack.nl (8.8.5/8.8.2) id VAA02177; Fri, 14 Feb 1997 21:30:21 +0100 (MET) Message-ID: <19970214213021.WM27935@xaa.stack.nl> Date: Fri, 14 Feb 1997 21:30:21 +0100 From: xaa@stack.nl (Mark Huizer) To: lsmarso@panix.com (Larry Marso) Cc: questions@freebsd.org Subject: Re: cvsup for ports? References: X-Mailer: Mutt 0.60 Mime-Version: 1.0 In-Reply-To: ; from Larry Marso on Feb 14, 1997 13:37:55 -0500 Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Larry Marso writes: > I use cvsup to update -current /usr/src files. > > I noted a reference to the use of cvsup to keep a local /usr/ports directory up > to date. How is this done? Importantly, does this procedure pull the > distfiles? (The desirable answer would be, for most people I assume, NO). > If you take the example file in /usr/share/examples/cvsup/ports-supfile, you have a nice thing to work with, it does exactly what you want. The ports-all target does not fetch the distfiles. Mark Huizer