Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Nov 2012 10:13:40 -0500
From:      Michael Powell <nightrecon@hotmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: When Is The Ports Tree Going To Be Updated?
Message-ID:  <k900u9$62c$1@ger.gmane.org>
References:  <50B2A57A.3050500@tundraware.com> <50B2A8D8.90301@FreeBSD.org> <50B2AA07.8090103@tundraware.com> <201211251856.40381.lumiwa@gmail.com> <50B2BEE1.9030903@tundraware.com> <50B31AAB.6000903@FreeBSD.org> <50B36500.7040308@tundraware.com> <CAAdA2WMVmtdsC3zpjz3WsmdopsuavhcVTC8TFuG-n_auPB77rg@mail.gmail.com> <50B377F4.1020507@freebsd.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Matthew Seaman wrote:

[snip]
>> 
>> And now I need to find an alternative to handle the src updates using svn
>> or something...
> 
> SVN works, but isn't amazingly quick.  If you're on a release branch you
> can get the src (and just the src) using freebsd-update(8), which should
> be pretty speedy and which I think is going to be the officially blessed
> method for non-developers to keep up to date.  Although anyone will
> still be able to use SVN if they want to.
> 
> You'll need to tweak /etc/freebsd-update.conf slightly to get just the
> system sources.  It's pretty obvious what to do.
> 

As a result of the security incident I switched away from csup and am now 
using portsnap for ports, and svn for source. The only disconcerting item I 
noticed is the 500-some MB .svn directory now under /usr/src/.

Can using freebsd-update for source update(s) eliminate the need for this 
500MB waste of space? Or is there some switch for svn which could accomplish 
same?

Thanks - Mike





Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?k900u9$62c$1>