Date: Sat, 17 Nov 2012 16:51:11 +0100 From: "C. P. Ghost" <cpghost@cordula.ws> To: Polytropon <freebsd@edvax.de> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: how to correct corrupted ports tree? Message-ID: <CADGWnjVXg7rkmHrwDE5_%2BLwOtBsQy8=HgCj6vXwpAn8OqbzTeQ@mail.gmail.com> In-Reply-To: <20121117110203.38708832.freebsd@edvax.de> References: <50A718F5.8040806@dreamchaser.org> <20121117110203.38708832.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 17, 2012 at 11:02 AM, Polytropon <freebsd@edvax.de> wrote: > On Fri, 16 Nov 2012 21:56:21 -0700, Gary Aitken wrote: >> I don't see a way to force refetch of the actual ports files >> like "distinfo" when portsnap thinks the port is up to date. > > You cansolve the problem of "few per-file mismatches" by > using the traditional CVS approach of updating the ports > tree. Only files not matching the current (on-server) content > will be updated. CVSup/csup is deprecated now and shouldn't be used anymore: http://www.freebsd.org/news/2012-compromise.html We should stop advertizing it as a way to update the ports tree. svn or portsnap is the way to go now. -cpghost. -- Cordula's Web. http://www.cordula.ws/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADGWnjVXg7rkmHrwDE5_%2BLwOtBsQy8=HgCj6vXwpAn8OqbzTeQ>