builds successfully. however, still working through some bugs with iPXE.

extra/dist.build.ini

@@ -58,8 +58,9 @@ ver =
 dev = r00t^2
 
 ; Your email address.
-; This is only used for the commit message if you enable
-; sync:git.
+; This is only used for commit messages (sync:git),
+; or GPG-signing the releases (see the associated build
+; section items).
 email = bts@square-r00t.net
 
 ; What this distribution/project is used for.
@@ -196,6 +197,13 @@ gpgkey = 7F2D434B9741E8AC
 ; 1.) The default is probably fine.
 gpgkeyserver = pgp.mit.edu
 
+; Should we sign our release files? (See the GPG section)
+; 0.) Only accepts (case-insensitive):
+;	yes|no
+;	true|false
+;	1|0
+gpg = yes
+
 ; Where should we save the bootstrap tarballs?
 ; 0.) No whitespace
 ; 1.) Will be created if it doesn't exist
@@ -263,7 +271,7 @@ multiarch = yes
 ;	true|false
 ;	1|0
 ; If it is undefined, it is assumed to be no.
-ipxe = yes
+ipxe =
 
 ; This option should only be enabled if you are on a fairly
 ; powerful, multicore system with plenty of RAM. It will
@@ -278,6 +286,30 @@ ipxe = yes
 i_am_a_racecar = yes
 
 
+#---------------------------------------------------------#
+# This section controls settings for signing our release
+#	files. This is only used if build:gpg is
+#       yes/true/etc.
+#---------------------------------------------------------#
+[gpg]
+
+; What is a valid key ID that we should use to
+; *sign* our release files?
+; 0.) You will be prompted for a passphrase if your
+;     key has one/you don't have an open gpg-agent
+;     session.
+; 1.) If you leave this blank we will use the key
+;     we generate automatically earlier in the build
+;     process.
+; 2.) We will generate one if this is blank and you
+;     have selected sign as yes.
+mygpgkey =
+
+; What directory should we use for the above GPG key?
+; Make sure it contains your private key.
+mygpghome =
+
+
 #---------------------------------------------------------#
 # This section controls what we should do with the
 #	resulting build and how to handle uploads, if we
@@ -466,11 +498,11 @@ ssl_key = ${ssldir}/main.key
 [rsync]
 
 ; This is the rsync destination host.
-host = bdisk.square-r00t.net
+host = 
 
 ; This is the remote user we should use when performing the
 ; rsync push.
-user = root
+user = 
 
 ; This is the remote destination path we should use for
 ;	pushing via rsync.
@@ -479,4 +511,12 @@ user = root
 ; 2.) The path MUST be writable by rsync:user
 ; RECOMMENDED: you'll probably want to set http:(user|group)
 ;	to what it'll need to be on the destination.
-path = /srv/http/${bdisk:uxname}_ipxe
+path = 
+
+; Should we rsync over the ISO files too, or just the boot
+; files?
+; 0.) Only accepts (case-insensitive):
+;	yes|no
+;	true|false
+;	1|0
+iso = yes