[MacPorts] howto/ShareArchives2 modified

[MacPorts]

Changed page "howto/ShareArchives2" by arno+macports at alum.wpi.edu from 98.179.180.192*
Page URL: <https://trac.macports.org/wiki/howto/ShareArchives2>
Diff URL: <https://trac.macports.org/wiki/howto/ShareArchives2?action=diff&version=3>
Revision 3
Comment: Replaced /usr/local with /opt/local

-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: howto/ShareArchives2
=========================================================================
--- howto/ShareArchives2 (version: 2)
+++ howto/ShareArchives2 (version: 3)
@@ -34,7 +34,7 @@
 openssl rsa -in privkey.pem -out newprivkey.pem
 }}}
 
-The public and private keys can be stored anywhere as long as they are accessible to the following steps. This tutorial has them placed on the build system at '''/usr/local/share/macports/'''.
+The public and private keys can be stored anywhere as long as they are accessible to the following steps. This tutorial has them placed on the build system at '''/opt/local/share/macports/'''.
 
 Note: While the build system need only have access to the private key, it's a good idea to store both the public and private keys in the same location. The installation system should only have access to the public key.
 
@@ -55,7 +55,7 @@
 
 {{{
 openssl dgst -ripemd160 \
-    -sign /usr/local/share/macports/privkey.pem \
+    -sign /opt/local/share/macports/privkey.pem \
     -out /opt/local/var/macports/software/lighttpd/lighttpd-1.4.28_0+ssl+universal.darwin_10.i386-x86_64.tbz2.rmd160 \
     /opt/local/var/macports/software/lighttpd/lighttpd-1.4.28_0+ssl+universal.darwin_10.i386-x86_64.tbz2
 }}}
@@ -65,8 +65,8 @@
 {{{
 #!/bin/sh
 
-PRIVKEY="/usr/local/share/macports/macports-donnybrook.priv"
-PUBKEY="/usr/local/share/macports/macports-donnybrook.pub"
+PRIVKEY="/opt/local/share/macports/macports-donnybrook.priv"
+PUBKEY="/opt/local/share/macports/macports-donnybrook.pub"
 SOFTWARE="/opt/local/var/macports/software"
 
 # First, clear out any outdated signatures
@@ -133,7 +133,7 @@
 
 You should now be able to start the service...
 {{{
-/opt/local/sbin/lighttpd -D -f /usr/local/share/macports/macports-archives-lighttpd.conf
+/opt/local/sbin/lighttpd -D -f /opt/local/share/macports/macports-archives-lighttpd.conf
 }}}
 and view your software archives in a browser:
 [http://localhost:6267]
@@ -161,7 +161,7 @@
         <string>/opt/local/sbin/lighttpd</string>
         <string>-D</string>
         <string>-f</string>
-        <string>/usr/local/share/macports/macports-archives-lighttpd.conf</string>
+        <string>/opt/local/share/macports/macports-archives-lighttpd.conf</string>
     </array>
     <key>StandardErrorPath</key>
     <string>/var/log/macports-archives-lighttpd.out</string>
@@ -182,7 +182,7 @@
 
 Finally we're ready to actually fetch some archives.
 
-First, copy the public key to each client system that will be installing from archives. As before, '''/usr/local/share/macports/''' is a decent enough location.
+First, copy the public key to each client system that will be installing from archives. As before, '''/opt/local/share/macports/''' is a decent enough location.
 
 Now, MacPorts needs to be configured to fetch archives from the build system. The '''archive_site_local''' setting can be set to an IP, but it will likely be more convenient to use the Bonjour name of the local system. This name can be found in the '''Sharing''' preference pane.
 
@@ -193,7 +193,7 @@
 
 A line indicating the location of the public key must also be added to '''${prefix}/etc/macports/pubkeys.conf'''. Something like:
 {{{
-/usr/local/share/macports/pubkey.pem
+/opt/local/share/macports/pubkey.pem
 }}}
 
 

-------8<------8<------8<------8<------8<------8<------8<------8<--------

* The IP shown here might not mean anything if the user or the server is
behind a proxy.

--
MacPorts <http://www.macports.org/>
Ports system for Mac OS

This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on howto/ShareArchives2. If it was not you, please
report to .