Changes between Version 10 and Version 11 of howto/ShareArchives2

Timestamp:

Sep 7, 2011, 3:21:03 PM (13 years ago)

Author:

fracai

Comment:

Minor grammar and naming corrections.

howto/ShareArchives2

@@ -8 +8 @@
 == Introduction ==
 
-Users with multiple machines can save significant compilation effort by installing pre-built ports from binary archives that have been assembled on another system. Under previous MacPorts releases this [wiki:howto/ShareArchives involved] enabling archive mode on all systems, manually transferring archives, and sometimes manually unpacking the archive before proceeding with the installation. MacPorts 2.0.0 introduces features which permanently enables archive mode and includes support for fetching archives from local or remote sources.
+Users with multiple machines can save significant compilation effort by installing pre-built ports from binary archives that have been assembled on another system. Under previous MacPorts releases this [wiki:howto/ShareArchives involved] enabling archive mode on all systems, manually transferring archives, and sometimes manually unpacking the archive before proceeding with the installation. MacPorts 2.0.0 introduces features which permanently enable archive mode and includes support for fetching archives from local or remote sources.
 
 == Installation ==
@@ -14 +14 @@
 Note, this HowTo assumes a MacPorts installation prefix of '''/opt/local'''. If you have installed to an alternate location, please update the paths accordingly.
 
-Also, the installation steps will refer to a '''build''' and '''installation''' systems. The '''build''' system compiles, signs, and shares ports and archives. Each '''installation''' system retrieves the archives and installs the port, without having to compile anything.
+Also, the installation steps will refer to '''build''' and '''installation''' systems. The '''build''' system compiles, signs, and shares ports and archives. Each '''installation''' system retrieves the archives and installs the port, without having to compile anything.
 
 === Step 1: '''Generate signing keys''' ===
@@ -45 +45 @@
 === Step 2: '''Let's sign some packages''' ===
 
-Now that the keys are generated, we can test signing a package. Any archive will do; the following example uses '''archive.tbz'''. Your example should specify the full path to the private key, the archive, and the archive signature that should be named identically to the input archive and suffixed with '''.rmd160'''.
+Now that the keys are generated, we can test signing a package. Any file will do; the following example uses '''archive.tbz'''. Your example should specify the full path to the private key, the archive, and the archive signature that should be named identically to the input archive and suffixed with '''.rmd160'''.
 
 {{{
@@ -147 +147 @@
 You'll also want the lighttpd service to run at all times so your client machines are not deprived of access to the port archives. A simple LaunchD task will handle this:
 
-'''/Library/LaunchDaemons/org.macports.share-archives.plist'''
+'''/Library/LaunchDaemons/org.macports.lighttpd.share-archives.plist'''
 {{{
 <?xml version="1.0" encoding="UTF-8"?>
@@ -156 +156 @@
     <true/>
     <key>Label</key>
-    <string>org.macports.share-archives</string>
+    <string>org.macports.lighttpd.share-archives</string>
     <key>LowPriorityIO</key>
     <true/>