On Fri, 11 Jan 2013, Brian W. wrote:
When I tried the first time, it only grabbed a few folders, a second try
got me a conflict message. I then just whacked /usr/src and did the svn co
again, successfully.
An important difference is that if you modify a file in /usr/src, an svn
update will no
On 01/11/2013 04:51 PM, Brian W. wrote:
> When I tried the first time, it only grabbed a few folders, a second try
> got me a conflict message. I then just whacked /usr/src and did the svn co
> again, successfully.
>
> Brian
And when you want to update, you can just type
svn up /usr/src
>
>
>
When I tried the first time, it only grabbed a few folders, a second try
got me a conflict message. I then just whacked /usr/src and did the svn co
again, successfully.
Brian
On Fri, Jan 11, 2013 at 2:48 PM, David Wolfskill wrote:
> On Fri, Jan 11, 2013 at 02:45:10PM -0800, Brian W. wrote:
> >
On Fri, Jan 11, 2013 at 02:45:10PM -0800, Brian W. wrote:
> I had an existing /usr/src/ tree from previous csup sessions. After a bit
> of reading, it looks like all I need to do are these two steps?
>
> pkg_add -r subversion
> svn co svn://svn.freebsd.org/base/stable/8 /usr/src
>
> Is it really
I had an existing /usr/src/ tree from previous csup sessions. After a bit
of reading, it looks like all I need to do are these two steps?
pkg_add -r subversion
svn co svn://svn.freebsd.org/base/stable/8 /usr/src
Is it really that simple for a src update?
I have been using portsnap for years for
