How to use subversion to keep source, system and doc files up
wblock at wonkity.com
Fri Sep 28 17:19:21 UTC 2012
On Fri, 28 Sep 2012, Jamie Paul Griffin wrote:
> [ Warren Block wrote on Thu 27.Sep'12 at 14:11:39 -0600 ]
>> Yes. If a new version of a file conflicts with your local changes, svn
>> will complain and try to help resolve those conflicts.
> When I changed to svn, I completely remove or moved (mv(1)) the
> /usr/ports tree. Created a new /usr/ports and then used svn to pull in
> the collection. The same for the base course tree in /usr/src. It's my
> understanding you need to do that first. You can't use a mixed file
> system tree comprising cvs/csup and svn files. I'm sure Some will
> correct that if i'm wrong, but that's what I did and i've experienced
> no problems with it.
Right, but conflicts are what happen if you change files after the
checkout. For example, I have a couple of custom patches to source.
If new versions of the source are checked in to the FreeBSD svn
repository, and they conflict with my local changes, svn will give a
warning and help try to resolve them.
> The only noticeable difference is when updating my ports collection
> with svn, it's slower to update than say portsnap or cvs/csup. But
> it's not a major issue for me.
This seems to be highly variable, possibly depending on how often you
update. For me, svn is at least as fast as cvs, and it feels faster.
Might just be a lot of fast screen output. portsnap is easily the
slowest on my systems. But I update very often.
More information about the freebsd-questions