From owner-freebsd-questions Thu Jan 25 20:26:57 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mailout4-0.nyroc.rr.com (mailout4-1.nyroc.rr.com [24.92.226.166]) by hub.freebsd.org (Postfix) with ESMTP id CD14637B401 for ; Thu, 25 Jan 2001 20:26:37 -0800 (PST) Received: from twcny.rr.com (syr-24-161-98-3.twcny.rr.com [24.161.98.3]) by mailout4-0.nyroc.rr.com (8.11.2/RoadRunner 1.03) with ESMTP id f0Q4N3b11808 for ; Thu, 25 Jan 2001 23:23:04 -0500 (EST) Message-ID: <3A70FC6C.723D9CF5@twcny.rr.com> Date: Thu, 25 Jan 2001 23:26:21 -0500 From: Tom Parquette X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: CVS deleting ports? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please CC me on any replies. TIA. I'm trying to keep everying on my 4.2-STABLE system failry up to date. I have something going on with the ports that I do not understand. I've RTFM but I'm fuzzy on CVS and I'm more or less just following the instructions. (Sorry Greg, your CVS section didn't help me either.) When I manually add the files to the ports directory (all that seems to exist is an HTML file) I can build the port. The latest one is etherboot that I'm playing with. The problem that I do not understand is, when I do the next CVS run, it seems to delete everything I just added to the /usr/ports.... directory. I've transcribed my supfile below. My undetstanding was cvs-all would bring down "everything" (including the ports.) Any helo would be appreciated since I would not even call my self a CVS novice. Cheers... # usr/src/hercules-supfile *default host=cvsup3.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=RELENG_4 *default delete use-rel-suffix *default compress cvs-all -- Try not. Do or do not. Is no try. -- Yoda To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message