When Is The Ports Tree Going To Be Updated?
Matthew Seaman
matthew at freebsd.org
Mon Nov 26 15:38:37 UTC 2012
On 26/11/2012 15:13, Michael Powell wrote:
> 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/.
SVN keeps a 2nd pristine copy of everything you check out in that .svn
directory. It's necessary when you use it for development work, but
otherwise, as you say, a waste of space.
> 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?
freebsd-update will have some overhead -- it downloads changesets to
somewhere under /var before expanding them onto the system. I haven't
measured how much this amounts to compared to SVN, but I'd assume if you
limit yourself to updating just the system sources with freebsd-update
then it should use up less space than using SVN. Normally
freebsd-update would have updates to compiled programs as well, which
could move the goalposts significantly.
Cheers,
Matthew
More information about the freebsd-questions
mailing list