Changes between Version 94 and Version 95 of DownloadSource
- Timestamp:
- 05/19/19 02:37:41 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DownloadSource
v94 v95 65 65 66 66 {{{ 67 svn checkout https://svn.osgeo.org/grass/grass/branches/releasebranch_7_4 grass74_release68 # Subsequent updates:69 svn up67 git checkout releasebranch_7_4 68 # subsequent updates: 69 git pull 70 70 }}} 71 71 … … 75 75 76 76 {{{ 77 svn checkout https://svn.osgeo.org/grass/grass/branches/releasebranch_7_2 grass72_release78 # Subsequent updates:79 svn up77 git checkout releasebranch_7_2 78 # subsequent updates: 79 git pull 80 80 }}} 81 81 … … 88 88 89 89 {{{ 90 svn checkout https://svn.osgeo.org/grass/grass/branches/releasebranch_7_0 grass70_release91 # Subsequent updates:92 svn up90 git checkout releasebranch_7_0 91 # subsequent updates: 92 git pull 93 93 }}} 94 94 … … 98 98 99 99 {{{ 100 svn checkout https://svn.osgeo.org/grass/grass/branches/releasebranch_6_4 grass64_release 100 git clone https://github.com/OSGeo/grass-legacy.git 101 cd grass-legacy 102 git checkout releasebranch_6_4 101 103 }}} 102 104 … … 104 106 105 107 {{{ 106 svn checkout https://svn.osgeo.org/grass/grass/tags/release_20090609_grass_6_4_0RC5 grass640_rc5108 git checkout release_20090609_grass_6_4_0RC5 107 109 }}} 108 110 109 111 110 === Committing code to SVN(developers with write access) ===112 === Committing code to Git (developers with write access) === 111 113 112 Note: Write access to the Subversion repository is governed by [wiki:RFC/2_LegalAspectsOfCodeContributions RFC 2: Legal aspects of code contributions]. Committers should take care to use https for access, and use their [http://www.osgeo.org/osgeo_userid OSGeo Userid] for authentication. See also [wiki:HowToContribute How-To Contribute].114 Note: Write access to the Git repository is governed by [wiki:RFC/2_LegalAspectsOfCodeContributions RFC 2: Legal aspects of code contributions]. Committers should take care to use https/ssh for access, and use their [https://github.com GitHub Account] for authentication. See also [wiki:HowToContribute How-To Contribute] and [wiki:HowToGit How-To Git]. 113 115 114 A commit command might look something like: 115 116 {{{ 117 svn commit -m "Distinguish between raster and vector backends (bug #999)" main.c --username glynn 118 }}} 119 120 After your first commit SVN will remember your OSGeo user id and password so --username only has be used the first time. 121 122 To add a new directory, please use (after checking that tmp files were removed and file permissions are appropriate): 123 124 {{{ 125 svn add newdir 126 svn commit -m "New xyz functionality uploaded" newdir 127 }}} 128 129 130 == Subversion GRASS Addons source code repository == 116 == Git GRASS Addons source code repository == 131 117 132 118 ''Want to contribute? Read on [wiki:HowToContribute#WriteaccesstotheGRASS-Addons-SVNrepository here]'' 133 119 134 With the subversionclient software installed, the current GRASS Addons can be extracted using the command:120 With the Git client software installed, the current GRASS Addons can be extracted using the command: 135 121 136 122 {{{ 137 svn checkout https://svn.osgeo.org/grass/grass-addons grass_addons123 git clone https://github.com/OSGeo/grass-addons.git 138 124 }}} 139 125 140 Update access to the Subversion Addons repository is governed by [wiki:RFC/2_LegalAspectsOfCodeContributions RFC 2: Legal aspects of code contributions]. Committers should take care to use https for access, and use their [http://www.osgeo.org/osgeo_userid OSGeo Userid] for authentication. A commit command might look something like: 141 142 {{{ 143 svn commit -m "Stereo DEM creation" main.c --username glynn 144 }}} 145 146 After your first commit SVN will remember your OSGeo user id and password so --username only has to be used the first time. 147 148 To add a new directory, please use (after checking that tmp files were removed and file permissions are appropriate): 149 150 {{{ 151 svn add newdir 152 svn commit -m "New xyz functionality uploaded" newdir 153 }}} 154 155 == Subversion GRASS Sandbox source code repository == 156 157 The "sandbox" repository is a place for collaborative experiments and alpha-ware not quite ready for incubation in the addons repository. 158 GRASS developers can create directories for themselves and use it as they like, just keep everything GPL>=2 compatible in the usual way! 159 160 With the subversion client software installed, the Sandbox repository can be extracted with the command: 161 162 {{{ 163 svn checkout https://svn.osgeo.org/grass/sandbox grass-sandbox 164 }}} 165 166 Write access to the Subversion Sandbox repository is again governed by [wiki:RFC/2_LegalAspectsOfCodeContributions RFC 2: Legal aspects of code contributions]. Committers should take care to use https for access, and use their [http://www.osgeo.org/osgeo_userid OSGeo Userid] for authentication. Commit commands will follow the same method as for the addons repository shown above. 167 == Subversion GRASS repository dumpstreams == 168 169 Incremental dumpstreams of GRASS SVN repository are available at [http://svn.osgeo.org/dumps/grass/]. 170 126 Update access to the Git Addons repository is governed by [wiki:RFC/2_LegalAspectsOfCodeContributions RFC 2: Legal aspects of code contributions]. Committers should take care to use https/ssh for access, and use their [https://github.com GitHub Account] for authentication. See also [wiki:HowToContribute How-To Contribute] and [wiki:HowToGit How-To Git]. 171 127 172 128 == Online browseable live web interfaces to source code repository == 173 129 174 * TracBrowser interfaces: 175 * [http://trac.osgeo.org/grass/browser/grass/ GRASS SVN] 176 * [http://trac.osgeo.org/grass/browser/grass-addons/ GRASS Addons SVN] 177 * [http://trac.osgeo.org/grass/browser/grass-web/ GRASS Web SVN] 178 * [http://josef.fsv.cvut.cz/cgi-bin/viewcvs.cgi/?root=grass-osgeo ViewCVS interface] 179 (Subversion backup note: svnsync runs 3 times per day) 180 * [http://svn.osgeo.org/grass/ Raw SVN server HTML interface] 130 * !GitHub interfaces: 131 * [https://github.com/OSGeo/grass GRASS Core Repository] 132 * [https://github.com/OSGeo/grass-addons GRASS Addons Repository] 181 133 182 == SVN mirrors==134 == Historical SVN == 183 135 184 * http://svnmirror.osgeo.org is a mirror of all OSGeo repositories incl. GRASS that is on a 15 minute svnsync. The physical machine is located at TelaScience.org in San Diego, CA (USA). 185 * A second GRASS SVN mirror is [http://josef.fsv.cvut.cz/cgi-bin/viewcvs.cgi/?root=grass-osgeo here] at the Czech Technical University in Prague (CZ), Faculty of Civil Engineering. 136 While SVN history for many individual files exists back to 1999. GRASS source code has been migrated to Git in May 2019. 137 138 * http://svn.osgeo.org/grass 139 * Online browseable UI, https://trac.osgeo.org/grass/browser 186 140 187 141 == Historical CVS == … … 193 147 194 148 You can download the source code as it existed on a particular day as follows: 149 195 150 {{{ 196 svn co -r '{2008-09-01}' https://svn.osgeo.org/grass/grass/branches/develbranch_6 grass6_20080901 151 git checkout 'master@{2008-09-01}' 197 152 }}} 198 199 You can then step forward in time to another date as follows:200 {{{201 svn update -r '{2008-09-04}'202 }}}203 204 This can be useful to help narrow down which change introduced some weird behaviour.205 206 207 While SVN history for many individual files exists back to 1999, if you want to go back in time to GRASS 5 days you should use the GRASS 5 CVS instead. The directory layout was widely changed between GRASS 5 and 6 and the earliest version of GRASS 6 that will actually compile on its own will be just before the 5.7.0 development release.208 153 209 154 == Compilation notes for various operating systems ==