Changes between Version 8 and Version 9 of SourceCodeGit
- Timestamp:
- Jul 20, 2012, 5:12:31 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SourceCodeGit
v8 v9 4 4 Various versions of the code are available at any given point: 5 5 6 '''Development''' 6 == Development == 7 7 8 8 The '''master''' branch contains the latest source code for all components of BOINC. … … 10 10 Use it if you need a recently-added feature. 11 11 12 '''Client software''' 12 == Client software == 13 13 14 14 The client software (client and manager) is maintained as follows: … … 19 19 For example, the branch '''boinc_core_release_6_2''' is the code for the latest release of version 6.2. 20 20 21 '''Server software''' 21 == Server software == 22 22 23 23 For all software other than the client (i.e., server, web, and API) … … 35 35 than server_stable for server software'''. 36 36 37 = = Using Git ==37 = Using Git = 38 38 39 == = Recommended reading/watching ===39 == Recommended reading/watching == 40 40 41 41 * [http://vimeo.com/14629850 Getting Git]: 1 hour video (technical, but highly recommended) … … 43 43 * [http://git-scm.com/doc All the rest]: Cheat sheets, tutorials and more videos 44 44 45 == = Installation ===45 == Installation == 46 46 47 47 * On Windows, get a Git client like [SourceCodeGit/Windows Git for Windows (console) and TortoiseGit (GUI)]. … … 50 50 * Recommended free GUIs: [http://www.sourcetreeapp.com SourceTree], [http://gitx.laullon.com GitX] ([https://github.com/laullon/gitx latest]) 51 51 52 == = Read-only access (cloning / checkout code) ===52 == Read-only access (cloning / checkout code) == 53 53 54 54 Note: this will give you anonymous read-only access only. For direct write access, please refer to the next section. … … 64 64 and fill in the dialog with one of the above URLs. There is no need to add 'git clone' in front of it. 65 65 66 == = Direct write access ===66 == Direct write access == 67 67 68 68 Note: you don't need direct write access to contribute code to BOINC. Given the [http://git-scm.com/about/distributed distributed nature] of git you can also publish your contributions elsewhere (e.g. on [https://github.com GitHub]) or send your patches via mail (using {{{git format-patch}}}). 69 69 70 Direct write access to the official repositories in currently available via the SSH protocol (with public-key authentication). If you think you need direct write you should contact David Anderson and/or Rom Walton. They'll ask you for your public-key. Here's how you can create one and use it after you've been grated access to the repository: 70 Direct write access to the official repositories in currently available via the SSH protocol (with public-key authentication). If you think you need direct write you should contact David Anderson and/or Rom Walton. They'll ask you for your public-key.[[BR]] 71 Here's how you can create a public/private key pair and use it after you've been grated access to the repository: 71 72 72 73 ==== Windows users ==== … … 86 87 }}} 87 88 88 If you had to use a different key filename because of an existing key that you don't want to overwrite or reuse, you can define a so called ssh host alias that allows you to specify which key to use when accessing the BOINC repo. In order to do so, add the following to {{{~/.ssh/config}}} (create the file if necessary), assuming that you created the ssh key as {{{~/.ssh/boinc-key}}}: 89 If you had to use a different key filename because of an existing key that you don't want to overwrite or reuse, you can define a so called ssh host alias that allows you to specify which key to use when accessing the BOINC repo.[[BR]] 90 In order to do so, add the following to {{{~/.ssh/config}}} (create the file if necessary), assuming that you created the ssh key as {{{~/.ssh/boinc-key}}}: 89 91 {{{ 90 92 host boinc-git-server … … 103 105 Finally, send the ''public'' key to David or Rom. Important: the private key should never leave your system! Keep it safe! 104 106 105 = == Windows build dependencies ===107 = Windows build dependencies = 106 108 107 109 All the additional dependency files are now stored in [source:build-depends-vs2005 build-depends-vs2005], get them using {{{git clone git://isaac.ssl.berkeley.edu/build-depends-vs2005.git}}}. … … 127 129 When you have older source code, I found that deleting all previous source code and downloading it fresh, will fix the breaks in building BOINC. Make sure to backup your own code prior to deleting the source code. 128 130 129 = = Browsing source code via the web ==131 = Browsing source code via the web = 130 132 131 133 You can browse the boinc code via [/browser a web-based interface] ([http://boinc.berkeley.edu/git alternative]). 132 134 This is useful for getting individual files, or seeing the revision history. 133 135 134 = = Source code road map ==136 = Source code road map = 135 137 136 138 The BOINC source tree includes the following directories:
