Changes between Version 6 and Version 7 of archives

Timestamp:

Jul 3, 2011, 3:52:13 PM (13 years ago)

Author:

nerdling (Jeremy Lavergne)

Comment:

update information for beta/trunk

archives

@@ -1 +1 @@
  = Using Your Own Archives =
-MacPorts recently added the ability to verify archives when `archivemode` is enabled. Signing archives is basically a requirement now. This page will serve as a guide showing how to do this.
+MacPorts verifies archives when `archivemode` is enabled, making the signing archives a requirement. This page will serve as a guide showing how to do this.
 
  = Create Keys =
@@ -26 +26 @@
 {{{
 cd /archive/repository
-for i in */*/*/*tbz2; do openssl dgst -ripemd160 -sign ~/.ssh/privkey.pem.bare -out $i.rmd160 $i; done
+for i in */*tbz2; do openssl dgst -ripemd160 -sign ~/.ssh/privkey.pem.bare -out $i.rmd160 $i; done
 }}}
-Note that this saves the signatures along side the archives, by simply using `.rmd160` as a suffix. This is what MacPorts presently expects.
+Note that this saves the signatures along side the archives, by simply using `.rmd160` as a suffix. This is what MacPorts expects.
 
  = Configure MacPorts =
@@ -35 +35 @@
  * add path to this copy in pubkeys.conf
 
-I saved my key as `/opt/local/etc/macports/snc.pub` for simplicity. To avoid naming collisions I suggest adding all custom keys to just one file.
+I used `${prefix}/etc/macports/snc.pub` for simplicity.
 
  = Try It =
@@ -43 +43 @@
 Each day (really, every 30 minutes) new ports arrive and several are updated. Rather than rebuilding the whole tree you'll want to go after the ones with changes. This is easily achieved by the `find` command.
 {{{
-cd /opt/local/var/macports/sources/rsync.macports.org/release/ports
+cd ${prefix}/var/macports/sources/rsync.macports.org/release/ports
 sudo port selfupdate
 find . -name Portfile -mtime -1d  | while read i
@@ -51 +51 @@
 }}}
 
-As you build archives, you'll eventually come across an instance where you're upgrading an older version. Keeping these outdated archives around might be less than ideal. We can wipe them out by looping through the repository checking the versions against what's current.
+As you build archives, you'll eventually come across an instance where you're upgrading an older version. Keeping these outdated archives around might be less than ideal. We can wipe them out as we build the updates in the repository, checking the versions against what's current.
 {{{
 cd /archive/repository
 sudo port selfupdate
-for i in */*/*
+for i in *
 do
     port -q info --index --version `basename $i` | while read j
     do
-        ls $i | grep -v $j | while read k
+        ls "$i" | grep -v "$j" | while read k
         do
-            sudo rm -v $i/$k
+            sudo rm -v "$i/$k"
         done
     done
 done
 }}}
+
+This can also be accomplished using `rsync` between a build box and a web server. After syncing you'd run a `sign_archives` routine described above.
+{{{
+for i in ${prefix}/var/macports/software/*
+do
+    port -q info --index --version `basename $i` | while read j
+    do
+        rsync -az --delete --filter "P *$j*" "$i" snc@tazamahal.com:/var/www/macports/
+    done
+done
+ssh snc@tazamahal.com sign_archives.sh
+}}}