version: Setup-Subversion-1.6.6.msi



svnadmin create d:\svnReps






# [general]
# password-db = passwd


# [users]
# harry = harryssecret
# sally = sallyssecret

这是设置用户,一行一个,存储格式为“用户名 = 密码”,如可插入一行:admin = admin888,即为系统添加一个用户名为admin,密码为admin888的用户



方式一,run svnserve as daemon:

svnserve –d -r d:\svnReps


比如:$ svn checkout svn://

方式二:run svnserver as a service:

1.使用svnserve通过inetd(for *nix)

2.Run svnserve as a Microsoft Windows service.

C:\> sc create svn
binpath= "\"C:\Program Files\Subversion\bin\svnserve.exe\" --service -r d:\svnReps"
displayname= "Subversion Server"
depend= Tcpip
start= auto
这段命令注册了一个service,会自动启动subversion svnserver
Be careful about spaces in your commandline to be invoked. If a directory name contains spaces (or other characters that need escaping),
place the entire inner value of binpath in double-quotes, by escaping them。
C:\> net start svn
可以通过删除其定义删除服务:sc delete svn,只需要确定首先停止服务





anon-access = none
auth-access = write

password-db = passwd

realm = my first responsity


到此,svn 已经可以很好的工作了,下面的内容主要是与eclipse相关的。 访问svn可以使用svn://hostname









Updates and commits are separate

One of the fundamental rules of Subversion is that a “push” action does not cause a “pull,” nor the other way around. Just because you're ready to submit new changes to the repository doesn't mean you're ready to receive changes from other people. And if you have new changes still in progress, then svn update should gracefully merge repository changes into your own, rather than forcing you to publish them.

The main side effect of this rule is that it means a working copy has to do extra bookkeeping to track mixed revisions as well as be tolerant of the mixture. It's made more complicated by the fact that directories themselves are versioned.

For example, suppose you have a working copy entirely at revision 10. You edit the file foo.html and then perform an svn commit, which creates revision 15 in the repository. After the commit succeeds, many new users would expect the working copy to be entirely at revision 15, but that's not the case! Any number of changes might have happened in the repository between revisions 10 and 15. The client knows nothing of those changes in the repository, since you haven't yet run svn update, and svn commit doesn't pull down new changes. If, on the other hand, svn commit were to automatically download the newest changes, then it would be possible to set the entire working copy to revision 15—but then we'd be breaking the fundamental rule of “push” and “pull” remaining separate actions. Therefore, the only safe thing the Subversion client can do is mark the one file—foo.html—as being at revision 15. The rest of the working copy remains at revision 10. Only by running svn update can the latest changes be downloaded and the whole working copy be marked as revision 15.




First, you cannot commit the deletion of a file or directory that isn't fully up to date. If a newer version of the item exists in the repository, your attempt to delete will be rejected in order to prevent you from accidentally destroying changes you've not yet seen.

Second, you cannot commit a metadata change to a directory unless it's fully up to date. You'll learn about attaching “properties” to items in 第 3 章 高级主题. A directory's working revision defines a specific set of entries and properties, and thus committing a property change to an out-of-date directory may destroy properties you've not yet seen.