1 Anonymous CVS Access for the ISC DHCP Distribution 2 3The ISC DHCP distribution can be accessed using "anonymous" CVS. 4"Anonymous" cvs uses the CVS "pserver" mechanism to allow anybody on 5the Internet to access a CVS repository without having to register in 6any way. Anonymous CVS allows you to access changes as soon as the 7DHCP developers commit them, rather than having to wait for the next 8snapshot or patchlevel. Changes that have not yet been released yet 9are not guaranteed to work, but they can nonetheless be useful in many 10cases. 11 12 TABLE OF CONTENTS 13 14 1. What is anonymous CVS? 15 2. How can i start using it? 16 3. Checking out the latest code in a release 17 4. Checking out the latest code 18 5. Checking out a specific release 19 6. When to update 20 21 WHAT IS ANONYMOUS CVS? 22 23Anonymous CVS also allows you to browse through the history of the 24DHCP distribution, and examine the revision history of specific files 25to see how they have changed between revisions, to try to figure out 26why something that was working before is no longer working, or just to 27see when a certain change was made. 28 29 HOW CAN I START USING IT? 30 31To use anonymous CVS to access the DHCP distribution, you must first 32"log in". You should only need to do this once, but it is a 33necessary step, even though access is anonymous. Anonymous users log 34in as user "nobody", password "nobody". To do this, type: 35 36 cvs -d :pserver:nobody@dhcp.cvs.isc.org:/cvsroot login 37 38You will be prompted for a password - type "nobody". If you get some 39kind of error indicating that cvs doesn't know how to log you in, you 40are probably running an old version of cvs, and should upgrade. This 41should work with cvs version 1.10. 42 43Once you have logged in, you can check out a version of the DHCP 44distribution, so the next question is, which version? 45 46 CHECKING OUT THE LATEST CODE IN A RELEASE 47 48There are currently four major versions of the distribution - Release 491, Release 2, Release 3, and the current development tree. Releases 501, 2 and 3 are branches in the CVS repository. To check out the 51latest code on any of these branches, you would use a branch tag of 52RELEASE_1, RELEASE_2 or RELEASE_3 in the following command: 53 54 (setenv CVSROOT :pserver:nobody@dhcp.cvs.isc.org:/cvsroot; 55 cvs checkout -d dhcp-2.0 -r RELEASE_2 DHCP) 56 57Note that the example is for Release 2. 58 59 CHECKING OUT THE LATEST CODE 60 61To check out the current engineering version, use: 62 63 (setenv CVSROOT :pserver:nobody@dhcp.cvs.isc.org:/cvsroot; 64 cvs checkout -d dhcp-current DHCP) 65 66Note that the current engineering version is a work in progress, and 67there is no real guarantee that it will work for you. 68 69 CHECKING OUT A SPECIFIC RELEASE 70 71You can also check out specific versions of the DHCP distribution. 72There are three kinds of version tags you may find - alpha tags, beta 73tags and release tags. Alpha tags look like this: 74 75 V#-ALPHA-YYYYMMDD 76 77# is the release number. YYYYMMDD is the date of the release, with a 784-digit year, the month expressed as a number (January=1), and the day 79of the month specified as a number, with the first day of the month 80being 1. 81 82Beta tags look like this: 83 84 V#-BETA-%-PATCH-* 85 86Where # is the release number, % is the Beta number (usually 1) and * 87is the patchlevel. In the future there may also be beta tags that 88look like this: 89 90 V#-#-BETA-%-PATCH-* 91 92Where #-# is the major version followed by the minor version - for 93example, when the first 3.1 beta comes out, the tag will look like 94this: 95 96 V3-1-BETA-1-PATCH-0 97 98Release tags look like this: 99 100 V#-%-* 101 102Where # is the major version, % is the minor version, and * is the 103patchlevel. So the tag for 1.0pl2 is V1-0-2, and to check it out, 104you'd type: 105 106 (setenv CVSROOT :pserver:nobody@dhcp.cvs.isc.org:/cvsroot; 107 cvs checkout -d dhcp-1.0pl2 -rV1-0-2 DHCP) 108 109Whenever changes are checked in to the ISC DHCP repository, or files 110are tagged, a notice is sent to the dhcp-source-changes@isc.org 111mailing list. You can subscribe to this list by sending mail to 112dhcp-source-changes-request@isc.org, and you will then get immediate 113notification when changes are made. You may find the volume of mail 114on this list annoying, however. 115 116 WHEN TO UPDATE 117 118We do not recommend that you do an update immediately after you see a 119change on the dhcp-source-changes mailing list - instead, it's best to 120wait a while to make sure that any changes that change depends on have 121also been committed. Also, sometimes when development is being done 122on two machines, the developers will check in a tentative change that 123hasn't been tested at all so that they can update on a different 124machine and test the change. The best way to avoid accidentally 125getting one of these changes is to not update aggressively - when a 126change is made, wait a while before updating, to make sure that it's 127not going to be quickly followed by another change. 128 129 130