Changes between Version 1 and Version 2 of GettingSource


Ignore:
Timestamp:
Sep 12, 2010 5:05:55 AM (4 years ago)
Author:
kris
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GettingSource

    v1 v2  
    11= Getting the Source Code = 
    22 
    3 PC-BSD uses a Subversion source control repository, in which all source code is stored. This document briefly discusses the basics of use Subversion, for more detail visit the [http://svnbook.red-bean.com/ Subversion manual] 
     3PC-BSD uses a Subversion source control repository, in which all source code is stored. For information on using subversion, please take a look at the [http://svnbook.red-bean.com/ Subversion manual] 
    44 
    55Checking out the code is easy. Make sure you have the subversion client installed, then: 
     
    99svn co svn://svn.pcbsd.org/pcbsd 
    1010 
    11 For trunk only: 
    12 svn co svn://svn.pcbsd.org/pcbsd/trunk 
     11Current (Our active branch of development, where new features and ideas are implemented) 
     12svn co svn://svn.pcbsd.org/pcbsd/current 
    1313 
    14 For the 1.4 branch only: 
    15 svn co svn://svn.pcbsd.org/pcbsd/branches/1.4 
     14Stable (Source for the current major release branch, which mostly contains bugfixes and small improvements) 
     15svn co svn://svn.pcbsd.org/pcbsd/stable 
     16 
     17For the specific 8.0 branch only (Or substitute the version you wish to checkout here) 
     18svn co svn://svn.pcbsd.org/pcbsd/branches/8.0 
    1619}}} 
    1720 
     
    2528== Making Commits == 
    2629 
    27 First, you need a Subversion username and password before you can commit changes into the tree. Contact Tim, Kris, or the development mailing list for one of these. 
    28  
    29 Once you have it, and you've made whatever changes to the files you want to commit, you're ready to check them into subversion. Checking in works recursively downwards like the 'svn up' command. So make sure you've changed directories so all the changes you've made are 'below' you in the filesystem to ensure all your changes are committed in one go. If they're not, you'll just have to make a second commit. The subversion command for a commit is: 
    30  
    31 {{{ 
    32 svn ci -m "Log message here" 
    33 }}} 
    34  
    35 Please try to make your log message as informative as possible. It should summarise the changes you made to the code. 
    36  
    37 === Adding files === 
    38  
    39 A commit will only checkin changes you've made to files already in the repository. If you want to add a new file to the repository, you need to add it to Subversion before committing it: 
    40  
    41 {{{ 
    42 svn add source.cpp 
    43 }}} 
    44  
    45 The add command supports wildcard matching. *.cpp for example. Once the files are added, you'll need to commit them as discussed earlier. 
    46  
    47 === Removing files === 
    48  
    49 Sometimes, you're going to want to remove a file from the repository altogether. Probably because it's no longer needed, but sometimes because you added it by accident. The method for doing this is similar to the add command. Don't remove it from your filesystem yourself, instead: 
    50  
    51 {{{ 
    52 svn rm source.cpp 
    53 }}} 
    54  
    55 Like the add command, rm supports wildcard matching. Once the file has been removed, you need to commit the change as discussed earlier. 
     30First, you need a Subversion username and password before you can commit changes into the tree. Please take a look at the [http://www.pcbsd.org/content/view/16/30/ Developers Page] for information on becoming a committer.