| | 49 | First, tell subversion to use your proxy to connect to the server: |
| | 50 | 1. If $prefix/var/macports/home/.subversion/servers doesn't exist, create it by copying the corresponding file from another user. (SVN automatically creates this file if it doesn't exist.) |
| | 51 | 2. Edit the file and set a proxy for hosts at `*.macports.org`. Different proxy configurations require different sets of options here, but the file is pretty well commented, so it should be easy to figure out what you need. At a minimum you'll need settings for http-proxy-host and http-proxy-port. |
| | 52 | |
| | 53 | Finally, if you want to use SVN over HTTPS to access the repository, you'll need to tell SVN to trust the MacPorts signature. (SVN doesn't trust the authority that issued it, and `port sync` below invokes `svn up` with the `--non-interactive` flag, so you won't have the opportunity to accept the certificate then.) |
| | 54 | 1. `mkdir -p $prefix/var/macports/home/.subversion/auth/svn.ssl.server` |
| | 55 | 2. As a normal user, run `svn ls https://svn.macports.org/repository/macports/trunk/dports/`. When prompted, accept the certificate permanently. |
| | 56 | 3. SVN will store the certificate in a file in the directory `$HOME/.subversion/auth/svn.ssl.server`. In that directory, find the file that contains the string "`https://svn.macports.org`" and copy it into `$prefix/var/macports/home/.subversion/auth/svn.ssl.server`. |
| | 57 | |
| | 58 | Or, you can use SVN over HTTP, in which case you don't need to worry about the certificate. |
