Subversion Repositories SvarDOS

Rev

Rev 873 | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 873 Rev 884
Line 97... Line 97...
97
=== MIRRORING THE PROJECT'S SVN ===============================================
97
=== MIRRORING THE PROJECT'S SVN ===============================================
98
 
98
 
99
Mirroring the project's svn tree (containing all build scripts, packages, etc)
99
Mirroring the project's svn tree (containing all build scripts, packages, etc)
100
is the best way to make a backup copy of the entire SvarDOS build system along
100
is the best way to make a backup copy of the entire SvarDOS build system along
101
with all its history. To achieve such mirror, one needs to create an empty
101
with all its history. To achieve such mirror, one needs to create an empty
102
svn repository and populate it using svnsync:
102
svn repository:
103
 
103
 
104
$ svnadmin create /srv/svardos-mirror
104
$ svnadmin create /srv/svardos-mirror
105
$ svnsync init file:///srv/svardos-mirror svn://svn.svardos.org/svardos
105
$ svnsync init file:///srv/svardos-mirror svn://svn.svardos.org/svardos
-
 
106
 
-
 
107
Then make this repository to accept modifications of revision properties, this
-
 
108
is mandatory so it can import historical data:
-
 
109
 
-
 
110
$ echo '#!/bin/sh' > /srv/svardos-mirror/hooks/pre-revprop-change
-
 
111
$ echo 'exi 0' >> /srv/svardos-mirror/hooks/pre-revprop-change
-
 
112
 
-
 
113
Finally, populate your mirror using svnsync (this operation has to be performed
-
 
114
periodically to keep your mirror up to date):
-
 
115
 
106
$ svn up /srv/svardos-mirror
116
$ svn up /srv/svardos-mirror
107
 
117
 
108
The same procedure can be used to migrate the SvarDOS build system from one
118
The same procedure can be used to migrate the SvarDOS build system from one
109
server to another.
119
server to another.
110
 
120
 
111
NOTE: The target svn server must allow modification of revision properties.
121
NOTE: Such mirror server must not be used to send commits to. The only process
112
      This is achieved with a svn "pre-revprop-change" hook of two lines:
122
      that should write to it is svnsync.
113
        #!/bin/sh
-
 
114
        exit 0
-
 
115
 
123
 
116
 
124
 
117
======================================================================= EOF ===
125
======================================================================= EOF ===