Version 15 (modified by mitty, 13 years ago) (diff) |
---|
Subversion
- Server/subversion - www.takebay.net/~nao
- Subversion のコンパイル (for Windows)
- How to create and apply a patch with Subversion
patch -p0 -i ~/fix_ugly_bug.diff
This will apply all the changes in the patch to your source. The -p0 option makes sure that all files can be found correctly (this has to do with something called ‘zero directories’, I won’t get into that right now). The -i option tells ‘patch’ what to use as input, in this case the ‘fix_ugly_bug.diff’ file in your home directory.
- Path-Based Authorization
- もうファイル管理で困らない! デザイナーのためのSubversion/TortoiseSVN入門 (Yahoo! JAPAN Tech Blog)
- |all variants| HOWTO: Upgrade to Subversion 1.7 - Ubuntu Forums
echo "deb http://opensource.wandisco.com/ubuntu lucid svn17" | sudo tee /etc/apt/sources.list.d/svn.list sudo wget -q http://opensource.wandisco.com/wandisco-debian.gpg -O- | sudo apt-key add - sudo apt-get update sudo apt-get dist-upgrade
Apache options
- Authorization Options > Blanket access control
- The parameters present on the Limit and LimitExcept directives are HTTP request types that are affected by that block. For example, if you wanted to disallow all access to your repository except the currently supported read-only operations, you would use the LimitExcept directive, passing the GET, PROPFIND, OPTIONS, and REPORT request type parameters. Then the previously mentioned Require valid-user directive would be placed inside the <LimitExcept> block instead of just inside the <Location> block.
<Location /svn> DAV svn SVNParentPath /var/svn # how to authenticate a user AuthType Basic AuthName "Subversion repository" AuthUserFile /path/to/users/file # For any operations other than these, require an authenticated user. <LimitExcept GET PROPFIND OPTIONS REPORT> Require valid-user </LimitExcept> </Location>
- The parameters present on the Limit and LimitExcept directives are HTTP request types that are affected by that block. For example, if you wanted to disallow all access to your repository except the currently supported read-only operations, you would use the LimitExcept directive, passing the GET, PROPFIND, OPTIONS, and REPORT request type parameters. Then the previously mentioned Require valid-user directive would be placed inside the <LimitExcept> block instead of just inside the <Location> block.
- 単純にRead-onlyにしたければ以下のようにすればよい see also #11
RedirectMatch ^/svn$ /svn/ <Location /svn/> # Requests for a collection must have a trailing slash on the URI. DAV svn SVNParentPath /path/to/svn SVNListParentPath on Order Allow,Deny Allow from all <LimitExcept GET PROPFIND OPTIONS REPORT> # read-only svn access Order Allow,Deny Deny from all </LimitExcept> </Location>
svn:externals
- ex) svn ps svn:externals 'libhoge https://example.jp/path/to/svn/outerrepos/trunk/libhoge' /path/to/workingcopy/trunk/fuga/
- svn up /path/to/workingcopy/trunk/fuga/
Fetching external item into '/path/to/workingcopy/trunk/fuga/libhoge' A /path/to/workingcopy/trunk/fuga/libhoge/piyo.php Updated external to revision 275.
- /path/to/workingcopy/trunk/fuga/libhoge/に幾つかファイルを追加後
- svn st /path/to/workingcopy/trunk/fuga/
M /path/to/workingcopy/trunk/fuga X /path/to/workingcopy/trunk/fuga/libhoge ? /path/to/workingcopy/trunk/fuga/libfuga.txt ? /path/to/workingcopy/trunk/fuga/readme.txt ? /path/to/workingcopy/trunk/fuga/fuga.php ? /path/to/workingcopy/trunk/fuga/favicon.ico Performing status on external item at '/path/to/workingcopy/trunk/fuga/libhoge' ? /path/to/workingcopy/trunk/fuga/libhoge/hoge ? /path/to/workingcopy/trunk/fuga/libhoge/hoge.php ? /path/to/workingcopy/trunk/fuga/libhoge/docs
- svn up /path/to/workingcopy/trunk/fuga/
setuid on NFS
- NFSマウントされたファイルシステム上で、リポジトリ作成後にchmod -R g+ws ${NEWREPOS}/db していると、commit時に以下のようなエラーになる
svn: Can't get exclusive lock on file '/var/svn/test/db/txn-current-lock': No locks available
- source:/trunk/TipAndDoc/tools/tool/buildrepos.sh
- chmod -R g+w ${NEWREPOS}/db でよい