Cvs.Intro 23 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364
  1. version=pmwiki-2.2.130 ordered=1 urlencoded=1
  2. agent=w3m/0.5.3+git20210102
  3. author=jrmu
  4. charset=UTF-8
  5. csum=
  6. ctime=1633619228
  7. host=38.87.162.47
  8. name=Cvs.Intro
  9. rev=17
  10. targets=Ircnow.SSHFingerprints
  11. text=!! Checkout code%0a%0aIn CVS, you '''check out''' a repo to download its files:%0a%0a[@%0a$ cvs -d anoncvs@example.com:/cvs checkout -P module%0a@]%0a%0aYou want to replace anoncvs@example.com with the username and hostname for the repo.%0a%0aYou'll also want to verify the SSH fingerprints. IRCNow publishes a list of known [[ircnow/SSHFingerprints|SSH fingerprints]].%0a%0aFor example, to check out code for ircnowd from anoncvs@anoncvs.ircnow.org, you'd run:%0a%0a[@%0a$ cvs -d anoncvs@anoncvs.ircnow.org checkout -P ircnowd%0a@]%0a%0aThe checkout commands produce a copy of the code in the '''working directory'''.%0a%0a!! Commit new code%0a%0aOnce you checkout a CVS repo, you can edit the code and save your changes. Until you commit your code, however, none of the updates will be saved in the CVS repository. '''WARNING''': Any code that is not committed will not be saved in the CVS repo.%0a%0aWhen you are ready to commit your code, type:%0a%0a[@%0a$ cvs commit%0a@]%0a%0aYou will be given a text editor (usually vi) to leave a commit message.%0a%0aTo commit and also write the message in a single command, type:%0a%0a[@%0a$ cvs commit -m "Your commit message goes here"%0a@]%0a%0a!! Update code%0a%0aTo update your working directory with new code from the repository, type:%0a%0a[@%0a$ cvs update%0a@]%0a%0a!! Add new files%0a%0a'''WARNING''': If you create a new file in your working directory, it will '''not''' automatically be added to the CVS repository. You must first run:%0a%0a[@%0a$ cvs add filename%0a@]%0a%0aReplace @@filename@@ with your real filename.%0a%0aThen, you must commit your changes with:%0a%0a[@%0a$ cvs commit%0a@]%0a%0aNote: @@cvs add@@ is only used for adding new files to a module that has already been checked out. If you want to add a new project to the repository, use @@cvs import@@ as described in '''Import New Repo'''.%0a%0a!! Remove files%0a%0aTo remove files from the CVS repo, it is not enough to simply delete them%0afrom the working directory. You will also want to remove them from the CVS repository:%0a%0a[@%0a$ cvs remove filename%0a@]%0a%0aAfterwards, you must commit this change to delete it from the repository:%0a%0a[@%0a$ cvs commit%0a@]%0a%0a!! Setting CVSROOT%0a%0aWhen working with CVS, it helps to set the CVSROOT, the path where the cvs folders are located:%0a%0aYou can set it for just the current shell:%0a%0a[@%0a$ export CVSROOT="anoncvs@example.com:/cvs"%0a@]%0a%0aIf CVS is local, you can use a file path:%0a%0a[@%0a$ export CVSROOT="/home/username/CVS"%0a@]%0a%0aAs a shortcut, you can add this to the bottom of your ~/.profile so you don't have to type it each time:%0a%0a[@%0a$ echo 'CVSROOT="anoncvs@example.com:/cvs"' >> ~/.profile%0a@]%0a%0aOnce CVSROOT is set, you can then omit the -d argument for checking out and committing code.%0a%0aSo the checkout code above becomes more simple:%0a%0a[@%0a$ cvs checkout -P module%0a@]%0a%0aAny time you check out code, the CVSROOT is automatically provided for the code in the working directory. So, it was not necessary to specify the CVSROOT for the commit command.%0a%0a!! Create New Repo%0a%0aTo create a new CVS repository, type:%0a%0a[@%0a$ cvs -d /path/to/CVS/ init%0a@]%0a%0aReplace @@/path/to/CVS/@@ with where you want the CVS repository to be located. For example, you might put it in @@~/CVS@@.%0a%0a!! Import New Module%0a%0aIf you have existing code that you'd like to import to a CVS repository, first change%0ato the folder containing the source code, then type:%0a%0a[@%0a$ cvs import reponame vendortag releasetag%0a@]%0a%0aReplace @@reponame@@, @@vendortag@@, and @@releasetag@@. CVS will put the source files inside a directory named @@reponame@@ inside the CVS root directory. @@vendortag@@ should be replaced with the vendor (the author) of the repository. @@releasetag@@ is the tag for the specific release.%0a%0aFor example:%0a%0a[@%0a$ cd ~/ircnowd/%0a$ cvs import ircnowd ircnow start%0a@]%0a%0a'''Note''': CVS does not automatically transform the imported source code into a working directory. As a result, any changes you make to the original source code directory cannot be committed to the CVS repo.%0a%0aTo fix this, you will need to checkout the source code. Change your directory to somewhere else to place the new working directory, then type:%0a%0a[@%0a$ cvs -d /path/to/CVS/ checkout -P reponame%0a@]%0a%0aReplace @@reponame@@ with the repository name. Then, change directory to @@reponame@@ to make changes. Afterwards, use cvs to commit them.%0a%0aIf checkout works properly, you can safely delete the old source code directory you imported from (since that one is not tracked by CVS).%0a%0a!! Export code%0a%0aEventually, when you are ready to use the code, you want to remove all the CVS-related files. To export code for use:%0a%0a[@%0a$ cvs -d anoncvs@example.com:/cvs export -D YYYYMMDD module%0a@]%0a%0aReplace @@YYYYMMDD@@ with the year, month, and day of the version of the repository you want to export. Replace @@module@@ with the module name.%0a%0a!! Troubleshooting%0a%0aIf you see this error message:%0a%0a[@%0acvs [commit aborted]: received broken pipe signal%0a@]%0a%0aIt may be because CVS was waiting for you to connect but your connection took too long. This can happen if you take too long to send a commit message or you take too long to provide passwords for your ssh keys. If this happens, try to find ways to avoid interactive input. For example, you might consider using the -m argument with cvs commit.%0a%0a[@%0acvs [server aborted]: cannot make directory /var/cvs/module: Permission denied%0a@]%0a%0aThis error message means that /var/cvs either doesn't exist or has the wrong permissions. If you're running cvs inside a chroot, check var/cvs inside the chroot. It needs to exist and be owned by the group commit and set to group writeable.%0a
  12. time=1634140189
  13. author:1634140189=jrmu
  14. diff:1634140189:1634136984:=154,160d153%0a%3c Eventually, when you are ready to use the code, you want to remove all the CVS-related files. To export code for use:%0a%3c %0a%3c [@%0a%3c $ cvs -d anoncvs@example.com:/cvs export -D YYYYMMDD module%0a%3c @]%0a%3c %0a%3c Replace @@YYYYMMDD@@ with the year, month, and day of the version of the repository you want to export. Replace @@module@@ with the module name.%0a
  15. host:1634140189=38.87.162.47
  16. author:1634136984=jrmu
  17. diff:1634136984:1634102164:=131c131%0a%3c Replace @@reponame@@, @@vendortag@@, and @@releasetag@@. CVS will put the source files inside a directory named @@reponame@@ inside the CVS root directory. @@vendortag@@ should be replaced with the vendor (the author) of the repository. @@releasetag@@ is the tag for the specific release.%0a---%0a> Replace @@reponame@@, @@vendortag@@, and @@releasetag@@. CVS will put the source files inside a directory named @@reponame@@ inside the CVS root directory. @@vendortag@@ should be replaced with the symbolic name of the branch. @@releasetag@@.%0a
  18. host:1634136984=38.87.162.47
  19. author:1634102164=jrmu
  20. diff:1634102164:1634101789:=140,150c140,147%0a%3c '''Note''': CVS does not automatically transform the imported source code into a working directory. As a result, any changes you make to the original source code directory cannot be committed to the CVS repo.%0a%3c %0a%3c To fix this, you will need to checkout the source code. Change your directory to somewhere else to place the new working directory, then type:%0a%3c %0a%3c [@%0a%3c $ cvs -d /path/to/CVS/ checkout -P reponame%0a%3c @]%0a%3c %0a%3c Replace @@reponame@@ with the repository name. Then, change directory to @@reponame@@ to make changes. Afterwards, use cvs to commit them.%0a%3c %0a%3c If checkout works properly, you can safely delete the old source code directory you imported from (since that one is not tracked by CVS).%0a---%0a> '''Note''': that CVS does not automatically convert this directory into %0a> %0a> Then to start, stay inside the SOURCEFOLDER and execute: [@$ cvs checkout REPONAME@]%0a> %0a> Then cd into REPONAME and make your changes%0a> %0a> Note: You are allowed to move the checked out folder%0a> %0a
  21. host:1634102164=38.87.162.47
  22. author:1634101789=jrmu
  23. diff:1634101789:1634099786:=112,115c112,116%0a%3c !! Create New Repo%0a%3c %0a%3c To create a new CVS repository, type:%0a%3c %0a---%0a> !! Import New Module%0a> %0a> If you have existing code that you'd like to import to a CVS repository, first change%0a> to the folder containing the source code, then type:%0a> %0a117c118%0a%3c $ cvs -d /path/to/CVS/ init%0a---%0a> $ cvs import reponame vendortag releasetag%0a120,126c121,124%0a%3c Replace @@/path/to/CVS/@@ with where you want the CVS repository to be located. For example, you might put it in @@~/CVS@@.%0a%3c %0a%3c !! Import New Module%0a%3c %0a%3c If you have existing code that you'd like to import to a CVS repository, first change%0a%3c to the folder containing the source code, then type:%0a%3c %0a---%0a> Replace @@reponame@@, @@vendortag@@, and @@releasetag@@. CVS will put the source files inside a directory named @@reponame@@ inside the CVS root directory. @@vendortag@@ should be replaced with the tag of the branch (such as 1.1.1). @@releasetag@@.%0a> %0a> For example:%0a> %0a128c126%0a%3c $ cvs import reponame vendortag releasetag%0a---%0a> $ cvs import ircnowd 1.1.1 1.1.1%0a131,134c129,134%0a%3c Replace @@reponame@@, @@vendortag@@, and @@releasetag@@. CVS will put the source files inside a directory named @@reponame@@ inside the CVS root directory. @@vendortag@@ should be replaced with the symbolic name of the branch. @@releasetag@@.%0a%3c %0a%3c For example:%0a%3c %0a---%0a> Note: versionname cannot have a '$.,:;#' in it%0a> %0a> !! Import New Repo%0a> %0a> To create a new CVS repository, type:%0a> %0a136,137c136%0a%3c $ cd ~/ircnowd/%0a%3c $ cvs import ircnowd ircnow start%0a---%0a> $ cvs -d /path/to/CVS/ init%0a140,141c139,146%0a%3c '''Note''': that CVS does not automatically convert this directory into %0a%3c %0a---%0a> Replace @@/path/to/CVS/@@ with where you want the CVS repository to be located. For example, you might put it in @@~/CVS@@.%0a> %0a> Then, change your directory to the folder with source code you want to import:%0a> %0a> [@%0a> $ cvs import reponame yourname versionname%0a> @]%0a> %0a147d151%0a%3c %0a
  24. host:1634101789=38.87.162.47
  25. author:1634099786=jrmu
  26. diff:1634099786:1634098969:=118c118%0a%3c $ cvs import reponame vendortag releasetag%0a---%0a> $ cvs import reponame yourname versionname%0a121,127c121%0a%3c Replace @@reponame@@, @@vendortag@@, and @@releasetag@@. CVS will put the source files inside a directory named @@reponame@@ inside the CVS root directory. @@vendortag@@ should be replaced with the tag of the branch (such as 1.1.1). @@releasetag@@.%0a%3c %0a%3c For example:%0a%3c %0a%3c [@%0a%3c $ cvs import ircnowd 1.1.1 1.1.1%0a%3c @]%0a---%0a> Replace reponame, yourname, and versionname.%0a
  27. host:1634099786=38.87.162.47
  28. author:1634098969=jrmu
  29. diff:1634098969:1634050145:=130c130%0a%3c $ cvs -d /path/to/CVS/ init%0a---%0a> $ cvs init%0a133,136c133,134%0a%3c Replace @@/path/to/CVS/@@ with where you want the CVS repository to be located. For example, you might put it in @@~/CVS@@.%0a%3c %0a%3c Then, change your directory to the folder with source code you want to import:%0a%3c %0a---%0a> Then, change your directory to the folder with source code and run:%0a> %0a146,147d143%0a%3c %0a%3c !! Export code%0a
  30. host:1634098969=38.87.162.47
  31. author:1634050145=jrmu
  32. diff:1634050145:1634047728:=
  33. host:1634050145=38.87.162.47
  34. author:1634047728=jrmu
  35. diff:1634047728:1634028691:=144,160d143%0a%3c %0a%3c %0a%3c !! Troubleshooting%0a%3c %0a%3c If you see this error message:%0a%3c %0a%3c [@%0a%3c cvs [commit aborted]: received broken pipe signal%0a%3c @]%0a%3c %0a%3c It may be because CVS was waiting for you to connect but your connection took too long. This can happen if you take too long to send a commit message or you take too long to provide passwords for your ssh keys. If this happens, try to find ways to avoid interactive input. For example, you might consider using the -m argument with cvs commit.%0a%3c %0a%3c [@%0a%3c cvs [server aborted]: cannot make directory /var/cvs/module: Permission denied%0a%3c @]%0a%3c %0a%3c This error message means that /var/cvs either doesn't exist or has the wrong permissions. If you're running cvs inside a chroot, check var/cvs inside the chroot. It needs to exist and be owned by the group commit and set to group writeable.%0a
  36. host:1634047728=38.87.162.47
  37. author:1634028691=jrmu
  38. diff:1634028691:1634028245:=16c16%0a%3c $ cvs -d anoncvs@anoncvs.ircnow.org checkout -P ircnowd%0a---%0a> cvs -d anoncvs@anoncvs.ircnow.org checkout -P ircnowd%0a112,116c112,115%0a%3c !! Import New Module%0a%3c %0a%3c If you have existing code that you'd like to import to a CVS repository, first change%0a%3c to the folder containing the source code, then type:%0a%3c %0a---%0a> !! Import New Repo%0a> %0a> Then init the CVS:%0a> %0a118c117%0a%3c $ cvs import reponame yourname versionname%0a---%0a> $ cvs init%0a121,138c120,124%0a%3c Replace reponame, yourname, and versionname.%0a%3c %0a%3c Note: versionname cannot have a '$.,:;#' in it%0a%3c %0a%3c !! Import New Repo%0a%3c %0a%3c To create a new CVS repository, type:%0a%3c %0a%3c [@%0a%3c $ cvs init%0a%3c @]%0a%3c %0a%3c Then, change your directory to the folder with source code and run:%0a%3c %0a%3c [@%0a%3c $ cvs import reponame yourname versionname%0a%3c @]%0a%3c %0a---%0a> Then import your files: [@$ cd SOURCEFOLDER; cvs import REPONAME YOURNAME VERSIONNAME@]%0a> %0a> Note: The VERSIONNAME cannot have a '$.,:;#' in it%0a> %0a> %0a140a127,128%0a> %0a> %0a143a132%0a> %0a
  39. host:1634028691=38.87.162.47
  40. author:1634028245=jrmu
  41. diff:1634028245:1634028073:=63c63%0a%3c Note: @@cvs add@@ is only used for adding new files to a module that has already been checked out. If you want to add a new project to the repository, use @@cvs import@@ as described in '''Import New Repo'''.%0a---%0a> Note: @@cvs add@@ is only used for adding new files to a module that has already been checked out. If you want to add a new project to the repository, use @@cvs import@@ described below.%0a
  42. host:1634028245=38.87.162.47
  43. author:1634028073=jrmu
  44. diff:1634028073:1634027029:=39,42c39,44%0a%3c !! Update code%0a%3c %0a%3c To update your working directory with new code from the repository, type:%0a%3c %0a---%0a> !! Setting CVSROOT%0a> %0a> When working with CVS, it helps to set the CVSROOT, the path where the cvs folders are located:%0a> %0a> You can set it for just the current shell:%0a> %0a44c46%0a%3c $ cvs update%0a---%0a> $ export CVSROOT="anoncvs@example.com:/cvs"%0a47,50c49,50%0a%3c !! Add new files%0a%3c %0a%3c '''WARNING''': If you create a new file in your working directory, it will '''not''' automatically be added to the CVS repository. You must first run:%0a%3c %0a---%0a> If CVS is local, you can use a file path:%0a> %0a52c52%0a%3c $ cvs add filename%0a---%0a> $ export CVSROOT="/home/username/CVS"%0a55,58c55,56%0a%3c Replace @@filename@@ with your real filename.%0a%3c %0a%3c Then, you must commit your changes with:%0a%3c %0a---%0a> As a shortcut, you can add this to the bottom of your ~/.profile so you don't have to type it each time:%0a> %0a60c58%0a%3c $ cvs commit%0a---%0a> $ echo 'CVSROOT="anoncvs@example.com:/cvs"' >> ~/.profile%0a63,69c61,64%0a%3c Note: @@cvs add@@ is only used for adding new files to a module that has already been checked out. If you want to add a new project to the repository, use @@cvs import@@ described below.%0a%3c %0a%3c !! Remove files%0a%3c %0a%3c To remove files from the CVS repo, it is not enough to simply delete them%0a%3c from the working directory. You will also want to remove them from the CVS repository:%0a%3c %0a---%0a> Once CVSROOT is set, you can then omit the -d argument for checking out and committing code.%0a> %0a> So the checkout code above becomes more simple:%0a> %0a71c66%0a%3c $ cvs remove filename%0a---%0a> $ cvs checkout -P module%0a73,110d67%0a%3c %0a%3c Afterwards, you must commit this change to delete it from the repository:%0a%3c %0a%3c [@%0a%3c $ cvs commit%0a%3c @]%0a%3c %0a%3c !! Setting CVSROOT%0a%3c %0a%3c When working with CVS, it helps to set the CVSROOT, the path where the cvs folders are located:%0a%3c %0a%3c You can set it for just the current shell:%0a%3c %0a%3c [@%0a%3c $ export CVSROOT="anoncvs@example.com:/cvs"%0a%3c @]%0a%3c %0a%3c If CVS is local, you can use a file path:%0a%3c %0a%3c [@%0a%3c $ export CVSROOT="/home/username/CVS"%0a%3c @]%0a%3c %0a%3c As a shortcut, you can add this to the bottom of your ~/.profile so you don't have to type it each time:%0a%3c %0a%3c [@%0a%3c $ echo 'CVSROOT="anoncvs@example.com:/cvs"' >> ~/.profile%0a%3c @]%0a%3c %0a%3c Once CVSROOT is set, you can then omit the -d argument for checking out and committing code.%0a%3c %0a%3c So the checkout code above becomes more simple:%0a%3c %0a%3c [@%0a%3c $ cvs checkout -P module%0a%3c @]%0a%3c %0a%3c Any time you check out code, the CVSROOT is automatically provided for the code in the working directory. So, it was not necessary to specify the CVSROOT for the commit command.%0a
  45. host:1634028073=38.87.162.47
  46. author:1634027029=jrmu
  47. diff:1634027029:1634026574:=6c6%0a%3c $ cvs -d anoncvs@example.com:/cvs checkout -P module%0a---%0a> cvs -d anoncvs@example.com:/cvs checkout -P module%0a23,26c23,26%0a%3c Once you checkout a CVS repo, you can edit the code and save your changes. Until you commit your code, however, none of the updates will be saved in the CVS repository. '''WARNING''': Any code that is not committed will not be saved in the CVS repo.%0a%3c %0a%3c When you are ready to commit your code, type:%0a%3c %0a---%0a> Once you checkout a CVS repo, you can edit the code and save your changes. However, until you commit your code, none of the updates will be saved in the CVS repository. Any code that is not committed will be lost if the checkout directory is deleted.%0a> %0a> When you are ready to commit your code (to store it in the repository).%0a> %0a31,38c31,32%0a%3c You will be given a text editor (usually vi) to leave a commit message.%0a%3c %0a%3c To commit and also write the message in a single command, type:%0a%3c %0a%3c [@%0a%3c $ cvs commit -m "Your commit message goes here"%0a%3c @]%0a%3c %0a---%0a> (Or if you wait to do it the quick way: [@$ cvs commit -m "COMMITMSG"@])%0a> %0a66c60%0a%3c $ cvs checkout -P module%0a---%0a> cvs checkout -P module%0a
  48. host:1634027029=38.87.162.47
  49. author:1634026574=jrmu
  50. diff:1634026574:1634026273:=2d1%0a%3c %0a19,20d17%0a%3c The checkout commands produce a copy of the code in the '''working directory'''.%0a%3c %0a27,32d23%0a%3c [@%0a%3c $ cvs commit%0a%3c @]%0a%3c %0a%3c (Or if you wait to do it the quick way: [@$ cvs commit -m "COMMITMSG"@])%0a%3c %0a63,70c54,57%0a%3c !! Import New Repo%0a%3c %0a%3c Then init the CVS:%0a%3c %0a%3c [@%0a%3c $ cvs init%0a%3c @]%0a%3c %0a---%0a> !! Import a new CVS repo%0a> %0a> Then init the CVS: [@$ cvs init@]%0a> %0a78,79c65,67%0a%3c %0a%3c %0a---%0a> Note: checkout only needed on first time%0a> %0a> %0a83a72,78%0a> %0a> Once you are done making changes:%0a> %0a> Commit the changes: [@$ cvs commit@] (Or if you wait to do it the quick way: [@$ cvs commit -m "COMMITMSG"@])%0a> %0a> %0a> Then it depends on if you have it remotely if you need to do some more steps%0a
  51. host:1634026574=38.87.162.47
  52. author:1634026273=jrmu
  53. diff:1634026273:1634025492:=1d0%0a%3c !! Checkout code%0a18,19c17,18%0a%3c !! Commit new code%0a%3c %0a---%0a> !! Committing new code%0a> %0a24,25c23,24%0a%3c !! Setting CVSROOT%0a%3c %0a---%0a> !! Settings CVSROOT%0a> %0a44,51d42%0a%3c @]%0a%3c %0a%3c Once CVSROOT is set, you can then omit the -d argument for checking out and committing code.%0a%3c %0a%3c So the checkout code above becomes more simple:%0a%3c %0a%3c [@%0a%3c cvs checkout -P module%0a
  54. host:1634026273=38.87.162.47
  55. author:1634025492=jrmu
  56. diff:1634025492:1634024206:=9,10c9,10%0a%3c You'll also want to verify the SSH fingerprints. IRCNow publishes a list of known [[ircnow/SSHFingerprints|SSH fingerprints]].%0a%3c %0a---%0a> You'll also want to verify the SSH fingerprints.%0a> %0a17,45c17,25%0a%3c !! Committing new code%0a%3c %0a%3c Once you checkout a CVS repo, you can edit the code and save your changes. However, until you commit your code, none of the updates will be saved in the CVS repository. Any code that is not committed will be lost if the checkout directory is deleted.%0a%3c %0a%3c When you are ready to commit your code (to store it in the repository).%0a%3c %0a%3c !! Settings CVSROOT%0a%3c %0a%3c When working with CVS, it helps to set the CVSROOT, the path where the cvs folders are located:%0a%3c %0a%3c You can set it for just the current shell:%0a%3c %0a%3c [@%0a%3c $ export CVSROOT="anoncvs@example.com:/cvs"%0a%3c @]%0a%3c %0a%3c If CVS is local, you can use a file path:%0a%3c %0a%3c [@%0a%3c $ export CVSROOT="/home/username/CVS"%0a%3c @]%0a%3c %0a%3c As a shortcut, you can add this to the bottom of your ~/.profile so you don't have to type it each time:%0a%3c %0a%3c [@%0a%3c $ echo 'CVSROOT="anoncvs@example.com:/cvs"' >> ~/.profile%0a%3c @]%0a%3c %0a%3c !! Import a new CVS repo%0a---%0a> %0a> Firstly set CVSROOT:%0a> %0a> if you have the CVS remotely: [@$ export CVSROOT="username@host.org:/home/username/CVS"@]%0a> %0a> if you have the CVS localy: [@$ export CVSROOT="/home/username/CVS"@]%0a> %0a> Note: Add that to your .profile, it will help you a lot%0a> %0a
  57. host:1634025492=38.87.162.47
  58. author:1634024206=jrmu
  59. diff:1634024206:1633619228:=1,2c1%0a%3c In CVS, you '''check out''' a repo to download its files:%0a%3c %0a---%0a> %0a7,10d5%0a%3c You want to replace anoncvs@example.com with the username and hostname for the repo.%0a%3c %0a%3c You'll also want to verify the SSH fingerprints.%0a%3c %0a16,49d10%0a%3c %0a%3c %0a%3c Firstly set CVSROOT:%0a%3c %0a%3c if you have the CVS remotely: [@$ export CVSROOT="username@host.org:/home/username/CVS"@]%0a%3c %0a%3c if you have the CVS localy: [@$ export CVSROOT="/home/username/CVS"@]%0a%3c %0a%3c Note: Add that to your .profile, it will help you a lot%0a%3c %0a%3c %0a%3c Then init the CVS: [@$ cvs init@]%0a%3c %0a%3c Then import your files: [@$ cd SOURCEFOLDER; cvs import REPONAME YOURNAME VERSIONNAME@]%0a%3c %0a%3c Note: The VERSIONNAME cannot have a '$.,:;#' in it%0a%3c %0a%3c %0a%3c Then to start, stay inside the SOURCEFOLDER and execute: [@$ cvs checkout REPONAME@]%0a%3c %0a%3c Note: checkout only needed on first time%0a%3c %0a%3c %0a%3c Then cd into REPONAME and make your changes%0a%3c %0a%3c Note: You are allowed to move the checked out folder%0a%3c %0a%3c %0a%3c Once you are done making changes:%0a%3c %0a%3c Commit the changes: [@$ cvs commit@] (Or if you wait to do it the quick way: [@$ cvs commit -m "COMMITMSG"@])%0a%3c %0a%3c %0a%3c Then it depends on if you have it remotely if you need to do some more steps%0a
  60. host:1634024206=38.87.162.47
  61. author:1633619228=jrmu
  62. diff:1633619228:1633619228:=1,10d0%0a%3c %0a%3c [@%0a%3c cvs -d anoncvs@example.com:/cvs checkout -P module%0a%3c @]%0a%3c %0a%3c For example, to check out code for ircnowd from anoncvs@anoncvs.ircnow.org, you'd run:%0a%3c %0a%3c [@%0a%3c cvs -d anoncvs@anoncvs.ircnow.org checkout -P ircnowd%0a%3c @]%0a
  63. host:1633619228=125.231.16.237