From owner-freebsd-questions@FreeBSD.ORG Tue Oct 19 15:25:47 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 A514316A4CE for ; Tue, 19 Oct 2004 15:25:47 +0000 (GMT) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B18443D1D for ; Tue, 19 Oct 2004 15:25:47 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend2.messagingengine.com (frontend2.internal [10.202.2.151]) by frontend1.messagingengine.com (Postfix) with ESMTP id 22763C330FD for ; Tue, 19 Oct 2004 11:25:46 -0400 (EDT) X-Sasl-enc: UB/uvxX5xVSGOh7pVYF0NA 1098199542 Received: from modem-2556.lion.dialup.pol.co.uk (modem-2556.lion.dialup.pol.co.uk [217.135.169.252]) by frontend2.messagingengine.com (Postfix) with ESMTP id 593B65700A2 for ; Tue, 19 Oct 2004 11:25:42 -0400 (EDT) From: "R. W." To: freebsd-questions@freebsd.org Date: Tue, 19 Oct 2004 16:25:43 +0100 User-Agent: KMail/1.7 References: <200410181506.55316.krinklyfig@spymac.com> In-Reply-To: <200410181506.55316.krinklyfig@spymac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410191625.44003.list-freebsd-2004@morbius.sent.com> Subject: Re: How to remove a patch from a port? 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: Tue, 19 Oct 2004 15:25:47 -0000 On Monday 18 October 2004 23:06, Joshua Tinnin wrote: > I'm wondering how to remove a custom patch for a port. I am sort of > new at this, but I've managed to learn how to patch a port and > upgrade it for testing. But I'm not at all sure how to remove that > patch if need be. What I've been doing is removing a chunk of the > ports tree with cd /usr/ports && rm -rf */*portname* and then > cvsup'ping again, but this doesn't seem right or very efficient. I've > read the man page for patch, but the only thing I can come up with is > the reverse option, which I must admit I don't totally understand. > Can anyone explain this in a way that makes sense? My understanding is that if a file has every been under cvs at a matching location in the tree, then CVSup will resync it (or delete it if it has been removed from the cvs tree). Any additional files will simply be ignored. All you need do is delete any files you have added and leave CVSup to do it's work. On the hand if all you have done is manually patch a file under the work directory, then a make clean should suffice - portupgrade will do that automatically when it builds something.