Date: Tue, 16 Jan 2001 12:46:08 +0200 From: Peter Pentchev <roam@orbitel.bg> To: Trevor Johnson <trevor@jpj.net> Cc: Peter Wemm <peter@netplex.com.au>, Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG>, Will Andrews <will@physics.purdue.edu>, ports@FreeBSD.ORG Subject: Re: overzealous cleaning of Attics in ports tree Message-ID: <20010116124608.A364@ringworld.oblivion.bg> In-Reply-To: <Pine.BSI.4.30.0101140430470.25832-100000@blues.jpj.net>; from trevor@jpj.net on Sun, Jan 14, 2001 at 07:06:10AM -0500 References: <200101122234.f0CMY9Q78574@mobile.wemm.org> <Pine.BSI.4.30.0101140430470.25832-100000@blues.jpj.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 14, 2001 at 07:06:10AM -0500, Trevor Johnson wrote: > > > I have a copy of everything that was deleted sitting on freefall in a > > .tar.gz. I really really do not want this cruft to go back into > > /home/ncvs/ports, but as a compromise how about leaving it extracted > > elsewhere? Perhaps even /home/ncvs/oldports ? That avoids the > > wasted time multiplied by the number of cvs updates multiplied by the > > number of developers, but still leaves it within reach IF necessary. > > I don't want to jump through hoops when dealing with removed files. In PR > 24276, David Gilbert writes: > > In the XFree86-4 port as installed by distribution CDROMs, there > are a number of patch files that have been deleted from the cvs > tree without being put in the attic. Even with "*default delete" > turned on in my supfile, patch-1 is not deleted and causes the > XFree86-4 port build to fail. > > This is a result of the purge, isn't it? I've had several friends run to me for help with exactly this situation - cvsup'ping yesterday from a 4.1-R ports tree, and winding up with several unapplicable yet undeleted patches - the CVS and cvsup servers no longer know anything about these patches, and the cvsup client refuses to delete files it does not recognize. Thanks for clearing up the mystery of the old patches lying around; any ideas as to how they can resolve that, short of rm -rf /usr/ports and pulling in a bright-and-shiny fresh new ports tree? :( [not always a perfect solution for people on slow modem links.. not too much good publicity either, I think :(( ] G'luck, Peter -- This sentence would be seven words long if it were six words shorter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010116124608.A364>