Cvs - Revision history

Sidetone: /* Historical usage of cvs */

2014-12-21T16:03:47Z

Historical usage of cvs

Sidetone at 16:01, 21 December 2014

2014-12-21T16:01:19Z

Sidetone at 15:59, 21 December 2014

2014-12-21T15:59:09Z

Sidetone: rough fixing up

2014-12-21T06:13:36Z

rough fixing up

Sidetone: copied and edited from Ports Tree, Updating

2014-12-21T06:09:50Z

copied and edited from Ports Tree, Updating

Sidetone: copied sections from Cvsup, and Updating the source tree (attribution). edits made too

2014-12-20T18:21:43Z

copied sections from Cvsup, and Updating the source tree (attribution). edits made too

Sidetone at 01:18, 18 December 2014

2014-12-18T01:18:52Z

Sidetone at 20:52, 17 December 2014

2014-12-17T20:52:30Z

Sidetone at 20:51, 17 December 2014

2014-12-17T20:51:56Z

Light at 16:03, 27 July 2005

2005-07-27T16:03:45Z

@@ Line 52: / Line 52: @@
 == Historical usage of cvs ==
 === How do I know which cvsup server to use? ===
-If you tried this recently, you can see that there are no or hardly any cvs servers to update FreeBSD.
+Examples of release tags that would have been chosen are at [[FreeBSD Release Branches]].
 The port <code>fastest_cvsup</code> takes (most of) the guess work out of finding the server that will be the fastest source for your location.   Once you've installed it, you can use it on the command-line something like this:

@@ Line 50: / Line 50: @@
 Save and close this file
 === How do I know which cvsup server to use? ===
 The port <code>fastest_cvsup</code> takes (most of) the guess work out of finding the server that will be the fastest source for your location.   Once you've installed it, you can use it on the command-line something like this:
@@ Line 66: / Line 70: @@
 Note that doing this does add a noticeable (10-15 seconds) delay while we locate the fastest server, and that that's really not something you generally need to do every time you update: it's generally better to go ahead and find the fastest server, then update your ports-supfile with it and leave it alone unless and until it starts to seem a lot slower than it used to / doesn't respond / etc.  Also note that we used backticks (`), not single quotes (').  That tells the shell to execute whatever is inside the backticks and use the results in the command that we gave it.
 === It's installed and configured; how do I update the ports tree? ===

@@ Line 4: / Line 4: @@
 You can optionally install [[cvsup]] (or ''cvsup-without-gui''). The cvsup program is the same as cvsup-without-gui if you do not have the X system installed, but many people prefer the non-gui version, as the ''cvsup'' version defaults to working in an X11 window (overridden with the -g flag).
 == Installing cvsup ==
@@ Line 70: / Line 67: @@
 Note that doing this does add a noticeable (10-15 seconds) delay while we locate the fastest server, and that that's really not something you generally need to do every time you update: it's generally better to go ahead and find the fastest server, then update your ports-supfile with it and leave it alone unless and until it starts to seem a lot slower than it used to / doesn't respond / etc.  Also note that we used backticks (`), not single quotes (').  That tells the shell to execute whatever is inside the backticks and use the results in the command that we gave it.
-== It's installed and configured; how do I update the ports tree? ==
+If you tried this recently, you can see that there are no or hardly any cvs servers to update FreeBSD, which brings us to the next section, about historical usage of cvs written out for archive.
 Once that's done, we're ready to actually update the ports. As root, issue this command:

@@ Line 27: / Line 27: @@
 and you'll get a ''lot'' of lines scrolling by; this is the program compiling.
-===Configuring your supfile===
+==Configuring your supfile==
 Csup uses the same supfile configuration as cvsup, and many of the commands for cvsup also apply to csup.
@@ Line 54: / Line 54: @@
 Save and close this file
-== It's installed and configured; how do I update the ports tree? ==
+=== How do I know which cvsup server to use? ===
-Once that's done, we're ready to actually update the ports. As root, issue this command:
-−
- # '''cvsup -g -L2 /root/ports-supfile_complete'''
-−
-In a perfect world, that will always work. The only times when it wont are when you don't have connectivity or the server that you're cvsup-ing against is not allowing connections. Strictly speaking, the ''-g'' command isn't necessary from a command line, since I installed cvsup-without-gui and the ''-g'' switch just makes sure that the GUI stuff in the regular CVSup program doesn't run. Since it isn't installed, I could have not given the switch and the command would have run just the same. The ''-L'' switch will give you error information, as well as a sort of progress-output -- the number next to the L (2 in this case) increases or decreases the verbosity of the output (0 is totally silent and 3 will give you everything you never wanted to read and more.) The last argument of the command is the actual ports-supfile that we made.
-−
 == How do I know which cvsup server to use? ==
 The port <code>fastest_cvsup</code> takes (most of) the guess work out of finding the server that will be the fastest source for your location.   Once you've installed it, you can use it on the command-line something like this:
@@ Line 73: / Line 66: @@
 We can also get fancy and do both things in a single step:
-  samizdata# '''/usr/local/bin/cvsup -h `/usr/local/bin/fastest_cvsup -Q -c us` /root/ports-supfile-complete'''
+  # '''/usr/local/bin/cvsup -h `/usr/local/bin/fastest_cvsup -Q -c us` /root/ports-supfile-complete'''
 Note that doing this does add a noticeable (10-15 seconds) delay while we locate the fastest server, and that that's really not something you generally need to do every time you update: it's generally better to go ahead and find the fastest server, then update your ports-supfile with it and leave it alone unless and until it starts to seem a lot slower than it used to / doesn't respond / etc.  Also note that we used backticks (`), not single quotes (').  That tells the shell to execute whatever is inside the backticks and use the results in the command that we gave it.
 ===Updating your source using the file===

@@ Line 5: / Line 5: @@
 You can optionally install [[cvsup]] (or ''cvsup-without-gui''). The cvsup program is the same as cvsup-without-gui if you do not have the X system installed, but many people prefer the non-gui version, as the ''cvsup'' version defaults to working in an X11 window (overridden with the -g flag).
-== Historical usage of cvs to update the source tree ==
+== Historical usage of cvs ==
 Here are examples of release tags that would be chosen, [[FreeBSD Release Branches]].
 ===Configuring your supfile===
@@ Line 12: / Line 31: @@
 Csup uses the same supfile configuration as cvsup, and many of the commands for cvsup also apply to csup.
-To use cvs, you should have a file named '''standard-supfile''' or something similer in '''/usr/share/examples/cvsup'''. Copy it somewhere else, such as into /root, and open the copy with a text editor. The following is the file that I use:
+Not so fast, speed racer. First you need to configure your ''supfile''. Go to /usr/share/examples/cvsup and look through the example files. The easiest way to make a ''supfile'' for your own personal use is to copy the one that want out of the examples and edit it. So from the command line, do a
   *default host=cvsup4.jp.FreeBSD.org   ''pick a nearby server from [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html#CVSUP-MIRRORS]''
   *default base=/var/db
@@ Line 24: / Line 53: @@
 Save and close this file
 ===Updating your source using the file===
 Assuming you have the supfile in your root directory named standard-supfile, run as root:
-  ''cd /root''
+  ''csup /root/standard-supfile''
- ''cvsup standard-supfile''
 or
- ''cd /root''
+  ''cvsup -g /root/standard-supfile''
   ''cvsup -g standard-supfile''
 The first time you run this command, it will probably take a significant amount of time. It will go out to the server you picked in the supfile, and attempt to update all of the source code needed to update FreeBSD to whatever version you have picked. Handbook references for gobs of details: [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/synching.html Other methods of getting source],  [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html Details and optional flags to cvsup].

@@ Line 1: / Line 1: @@
-'''cvs''' stands for Concurrent Versions System. As the name implies, it is a version control system. ''[[csup]]'', which comes with the base system, is useful to update ports from cvs repositories. [[cvsup]] may still be required for other mirroring tasks that don't apply to ports or updating sources.
+'''cvs''' stands for Concurrent Versions System. As the name implies, it is a version control system.
 For more information and the full documentation visit the [[http://cvshome.org offical website]].
 [[Category : System Commands]]

← Older revision		Revision as of 16:03, 27 July 2005
Line 1:		Line 1:
	'''cvs''' stands for Concurrent Versions System. As the name implies, it is a version control system.		'''cvs''' stands for Concurrent Versions System. As the name implies, it is a version control system.
		+
		+	For more information and the full documentation visit the [[http://cvshome.org offical website]].

	[[Category : System Commands]]		[[Category : System Commands]]