The detailed installation step of the Subversion, Google will know, just talk about some of the issues and precautions encountered during the installation process.
1. First $ project_name / conf / svnserve.conf file configuration requires attention. When you cancel Anon-Access = Read and Auth-Access = Write comments, it is also necessary to remove the annotations of [general], and the front space is also removed. Otherwise, you will tell you errors such as Line XXX Header Expected. Of course, if you use the password-db = passwd option, then your PASSWD file is also plus [users], add users and passwords, and the earth people do not necessarily know ^ _ ^.
2. Starting SVNServer's daemon should be svnserver -d -r $ project_path, no -install parameters, at least my 1.1.3 version is like this. The service as NT can be said with SVNService.
3. I use ZIP's decompression package to unwield you can use the EXE executable file in bin. Among them, there is garbled, based on research, CMD is set to set the environment variable of APR_ICONV_PATH = $ Project_Path, otherwise the corresponding language file will be found, and the Chinese becomes / xxx / xxx, but it does not affect the use. I think, this Subversion is not good.
.
Two DLLs in the decompression package are MSVCP60.DLL and INTL.DLL. If you use the EXE installation method, this problem will not occur. On the online Google is, if you ask me where the two DLLs can be used, I suggest you put it on the best in Mars.
3. Subversion and IIS. I want to use HTTP to access, and I don't have good Apache. Google has a SUVVERSION WORK ON IIS seems to have not found a solution. Which people know how to combine IIS, I will tell one or two.
Can you use HTTP to access remote access?
. Silly Y, you can use the SVN protocol, as for the client software, hey, there is a preference, free choice.
To here, everything is quiet!
