[MacPorts] howto/SyncingWithSVN modified

MacPorts noreply at macports.org
Tue Nov 1 04:42:43 CET 2016


Page "howto/SyncingWithSVN" was changed by ryandesign
Diff URL: <https://trac.macports.org/wiki/howto/SyncingWithSVN?action=diff&version=24>
Revision 24
Comment: Remove references to HTTP and require HTTPS
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: howto/SyncingWithSVN
=========================================================================
--- howto/SyncingWithSVN (version: 23)
+++ howto/SyncingWithSVN (version: 24)
@@ -1,6 +1,6 @@
 [wiki:howto <- Back to the HOWTO section]
 
-= How to sync your ports tree using Subversion (over HTTP(s)) =
+= How to sync your ports tree using Subversion over HTTPS
 
 - Audience: end users who cannot use rsync (873/tcp) due to firewalls,
   proxies, policy, etc.
@@ -10,10 +10,7 @@
 
 == Introduction ==
 
-Some people live and work behind a firewall or proxy that blocks or
-otherwise breaks rsync, which is the primary means of getting updated
-portfiles in MacPorts. The following steps will switch your tree over to
-using Subversion (over https) for syncing.
+Some people live and work behind a firewall or proxy that blocks or otherwise breaks rsync, which is the primary means of getting updated Portfiles in MacPorts. The following steps will switch your tree over to using Subversion over HTTPS for syncing.
 
 Note: if you are using a custom prefix, you will have to replace the default of `/opt/local` with the location of your MacPorts install in the instructions below.
 
@@ -39,12 +36,6 @@
 cd svn.macports.org/trunk/dports 
 svn co https://svn.macports.org/repository/macports/trunk/dports/ .
 }}}
-If you prefer, the repository is also available via HTTP, which requires
-less configuration, but is seen as less secure (subject to a man in the
-middle attack).
-{{{
-svn co http://svn.macports.org/repository/macports/trunk/dports/ .
-}}}
 
 
 == Configuration ==
@@ -57,21 +48,20 @@
 
 {{{
 #rsync://rsync.macports.org/macports/release/tarballs/ports.tar [default]
-file://opt/local/var/macports/sources/svn.macports.org/trunk/dports/ [default]
+file:///opt/local/var/macports/sources/svn.macports.org/trunk/dports/ [default]
 }}}
 
 === Step 3: Configure Subversion ===
 
-First, tell subversion to use your proxy to connect to the server.  This
-should not be necessary if your initial SVN checkout was from the http
-or https URL's (and the checkout worked), so most people should not have
+First, tell Subversion to use your proxy to connect to the server.  This
+should not be necessary if your initial Subversion checkout worked, so most people should not have
 to do this.  If initial checkout failed, you will need this.  If you
 needed to configure your own ~/.subversion/servers file to be able to do
 the initial checkout, then you *do* need this step.
 
 1. If the /opt/local/var/macports/home/.subversion/servers file doesn't
    exist, create it by copying the corresponding ~/.subversion/servers
-   file from another user to that location.  (SVN automatically creates
+   file from another user to that location.  (Subversion automatically creates
    this file if it doesn't exist, so you probably already have one.)
 1. Edit the file and set a proxy for hosts at `*.macports.org`.
    Different proxy configurations require different sets of options
@@ -79,24 +69,15 @@
    figure out what you need.  At a minimum you'll need settings for
    http-proxy-host and http-proxy-port.
 
-Finally, if you want to use SVN over HTTPS to access the repository
-(i.e. if your initial SVN checkout was the !https:// URL), 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.)
+Finally, if you're using the copy of `svn` that comes bundled with OS X 10.7 or later, you'll need to tell Subversion to trust the MacPorts signature.  (Apple's `svn` doesn't trust any SSL certificates, and `port sync` below invokes `svn up` with the `--non-interactive` flag, so you won't have the opportunity to accept the certificate then.)
 
 1. `mkdir -p /opt/local/var/macports/home/.subversion/auth/svn.ssl.server`
 1. As a normal user, run `svn ls https://svn.macports.org/repository/macports/trunk/dports/`.
    When prompted, accept the certificate permanently.
-1. SVN will store the certificate in a file in the directory
+1. Subversion 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 `/opt/local/var/macports/home/.subversion/auth/svn.ssl.server`.
-
-Or, you can use SVN over HTTP (i.e. your initial checkout was from the
-!http:// URL), in which case you don't need to worry about the
-certificate.
 
 === Step 4: Sync ===
 
@@ -110,7 +91,7 @@
 
 == See also ==
 
-Additional topics related to MacPorts and SVN:
+Additional topics related to MacPorts and Subversion:
 
 - Creating and testing ports not yet submitted to MacPorts:
   [https://guide.macports.org/#development.local-repositories Local development repository]
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://trac.macports.org/wiki/howto/SyncingWithSVN>
MacPorts <https://www.macports.org/>
Ports system for macOS

This is an automated message. Someone added your email address to be
notified of changes on 'howto/SyncingWithSVN' page.
If it was not you, please report to admin at macports.org.


More information about the macports-changes mailing list