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 ports, so I can continue to do that. Brian
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 that simple for a src update?Unless you have custom modifications in your source tree, I believe that you will find it simpler to remove it (or at least rename it) and use the above "svn co" to create a fresh new working copy.> I have been using portsnap for years for ports, so I can continue to do > that.That is my understanding, yes.> ...Peace, david -- David H. Wolfskill david at catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20130111/5bff40a6/attachment.sig>
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 <david at catwhisker.org>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 that simple for a src update? > > Unless you have custom modifications in your source tree, I believe that > you will find it simpler to remove it (or at least rename it) and use > the above "svn co" to create a fresh new working copy. > > > I have been using portsnap for years for ports, so I can continue to do > > that. > > That is my understanding, yes. > > > ... > > Peace, > david > -- > David H. Wolfskill david at catwhisker.org > Taliban: Evil men with guns afraid of truth from a 14-year old girl. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. >
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. > > BrianAnd when you want to update, you can just type svn up /usr/src> > > On Fri, Jan 11, 2013 at 2:48 PM, David Wolfskill <david at catwhisker.org>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 that simple for a src update? >> >> Unless you have custom modifications in your source tree, I believe that >> you will find it simpler to remove it (or at least rename it) and use >> the above "svn co" to create a fresh new working copy. >> >>> I have been using portsnap for years for ports, so I can continue to do >>> that. >> >> That is my understanding, yes. >> >>> ... >> >> Peace, >> david >> -- >> David H. Wolfskill david at catwhisker.org >> Taliban: Evil men with guns afraid of truth from a 14-year old girl. >> >> See http://www.catwhisker.org/~david/publickey.gpg for my public key. >> > _______________________________________________ > freebsd-stable at freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" > >
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 not overwrite it but try to merge with new versions of the file from the repository.