Date: Sun, 18 Nov 2012 06:58:29 +0100 From: Polytropon <freebsd@edvax.de> To: "C. P. Ghost" <cpghost@cordula.ws> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: how to correct corrupted ports tree? Message-ID: <20121118065829.7a20efe6.freebsd@edvax.de> In-Reply-To: <CADGWnjVXg7rkmHrwDE5_%2BLwOtBsQy8=HgCj6vXwpAn8OqbzTeQ@mail.gmail.com> References: <50A718F5.8040806@dreamchaser.org> <20121117110203.38708832.freebsd@edvax.de> <CADGWnjVXg7rkmHrwDE5_%2BLwOtBsQy8=HgCj6vXwpAn8OqbzTeQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 17 Nov 2012 16:51:11 +0100, C. P. Ghost wrote: > 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. Thank you for changing my inner attitude toward the new technology. I will try to avoid what "just works" (and now "worked", past tense). :-) I really hope a SVN equivalent like csup (a CVS implementation that is part of the _base_ system) will appear so there is no need to install something from ports (like cvsup-without-gui in the past). It should be efficient, fast, and free of bloat. It should also be easy to integrate it into basic operations (as shown in my example with the sup/ config file and the entry in /etc/make.conf, making "make update" a simple task, both for OS sources and ports). When this is _granted_, one could think about removing it from the base OS install. Note that I did mention it because it worked all the years fast and flawlessly, and I'm using CVS myself for "archiving" configuration files of different systems locally. I never thought about migrating this stuff over to SVN, because I consider it "too voluminous". Maybe I'm wrong, and I should be corrected. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121118065829.7a20efe6.freebsd>