checking in- currently trying to get the cleanup sorted. i need something that works better, i think

extra/dist.build.ini

@@ -123,6 +123,72 @@ password =
 #---------------------------------------------------------#
 [build]
 
+; What is the mirror for your bootstrap tarball?
+; It is *highly* recommended you use an Arch Linux tarball
+; as the build process is highly specialized to this.
+; 0.) No whitespace
+; 1.) Must be accessible remotely (no local file paths)
+mirror = mirror.us.leaseweb.net
+
+; What is the protocol for the bootstrap mirror?
+; 0.) Must be one of:
+; 	http, https, ftp
+mirrorproto = https
+
+; What is the path to the tarball directory?
+; 0.) Must be a complete path
+; 	(e.g. /dir1/subdir1/subdir2/
+; 1.) No whitespace
+mirrorpath = /archlinux/iso/latest/
+
+; What is the filename for the tarball found in the above?
+; If left blank, we will use the sha1 checksum file to try
+; to guess the most recent file.
+mirrorfile = 
+
+; What is the path to a sha1 checksum file?
+; 0.) No whitespace
+; 1.) Must be the full path
+; 2.) Don't include the mirror domain or protocol
+mirrorchksum = ${mirrorpath}sha1sums.txt
+
+; Optional GPG checking.
+; If the file has a GPG signature file,
+; we can use it for extra checking.
+; If it's blank, GPG checking will be disabled.
+; If you specify just '.sig' (or use the default
+; and don't actually specify a mirrorfile),
+; we'll try to guess based on the file from the sha1
+; checksums.
+; 0.) No whitespace (if specified)
+; 1.) Must be the full path
+; 2.) Don't include the mirror domain or protocol
+mirrorgpgsig = ${mirrorfile}.sig
+
+; What is a valid key ID that should be used to
+; verify the tarballs?
+; 0.) Only used if mirrorgpgsig is set
+; 1.) Should be in the "shortform"
+;	(e.g. 7F2D434B9741E8AC)
+gpgkey = 7F2D434B9741E8AC
+
+; What is a valid keyserver we should use
+; to fetch gpgkey?
+; 0.) Only used if mirrorgpgsig is set
+; 1.) The default is probably fine.
+gpgkeyserver = pgp.mit.edu
+
+; Where should we save the bootstrap tarballs?
+; 0.) No whitespace
+; 1.) Will be created if it doesn't exist
+dlpath = /var/tmp/${bdisk:uxname}
+
+; Where should the bootstrap tarballs extract to and the
+; chroots be built?
+; 0.) No whitespace
+; 1.) Will be created if it doesn't exist
+chrootdir = /var/tmp/chroots
+
 ; Where is the base of the BDisk project located?
 ; In other words, if you cloned BDisk from git,
 ; what is BDisk's working tree directory?
@@ -164,9 +230,10 @@ mountpt = /mnt/${bdisk:uxname}
 ; Should we build a multiarch image? That is to say, the
 ; same ISO file can be used for both i686 and x86_64.
 ; 0.) Only accepts (case-insensitive):
-;	yes|no
-;	true|false
-;	1|0
+;	yes/true (buld both i686, x86_64 in same image)
+;	no/false (build separate images, both arch's)
+;	i686	 (ONLY build i686 architecture)
+;	x86_64	 (ONLY build x86_64 architecture)
 ; If it is undefined, it is assumed to be no.
 multiarch = yes
 
@@ -181,10 +248,9 @@ multiarch = yes
 ipxe = yes
 
 ; This option should only be enabled if you are on a fairly
-;	powerful, multicore system with plenty of RAM.
-; It will speed the build process along, but will have
-;	some seriously adverse effects if your system
-;	can't handle it.
+; powerful, multicore system with plenty of RAM. It will
+; speed the build process along, but will have some
+; seriously adverse effects if your system can't handle it.
 ; Most modern systems should be fine with leaving it enabled.
 ; 0.) Only accepts (case-insensitive):
 ;	yes|no
@@ -212,9 +278,9 @@ i_am_a_racecar = yes
 http = yes
 
 ; Should we generate/prepare TFTP files?
-; This is mostly only useful if you plan on using more 
-;	traditional (non-iPXE) setups and regualar PXE
-;	bootstrapping into iPXE.
+; This is mostly only useful if you plan on using more
+; traditional (non-iPXE) setups and regualar PXE bootstrapping
+; into iPXE.
 ; 0.) Only accepts (case-insensitive):
 ;	yes|no
 ;	true|false
@@ -223,19 +289,18 @@ http = yes
 tftp = yes
 
 ; Enable automatic Git pushing for any changes done to the
-;	project itself?
-; If you don't have upstream write access, you'll want to
-;	set this to False.
+; project itself? If you don't have upstream write access,
+; you'll want to set this to False.
 ; 0.) Only accepts (case-insensitive):
 ;	yes|no
 ;	true|false
 ;	1|0
 ; If it is undefined, it is assumed to be no.
-git = yes
+git = no
 
 ; Enable rsync pushing for the ISO (and other files, if
 ; you choose- useful for iPXE over HTTP(S)).
-rsync = yes
+rsync = no
 
 
 #---------------------------------------------------------#
@@ -275,8 +340,8 @@ group = http
 path = ${build:basedir}/tftpboot
 
 ; What user and group, if applicable, should the TFTP files
-;	be owned as? This is most likely going to be either
-;	'tftp' or 'root'.
+; be owned as? This is most likely going to be either 'tftp'
+; or 'root'.
 ; 0.) No whitespace
 ; 1.) User must exist on system
 ; 2.) If sync:tftpdir is blank, they will not be used
@@ -291,9 +356,9 @@ group = root
 [ipxe]
 
 ; Build a "mini-ISO"; that is, an ISO file that can be used
-;	to bootstrap an iPXE environment (so you don't need
-;	to set up a traditional PXE environment on your LAN).
-;We'll still build a full standalone ISO no matter what.
+; to bootstrap an iPXE environment (so you don't need to set
+; up a traditional PXE environment on your LAN). We'll still
+; build a full standalone ISO no matter what.
 ; 0.) Only accepts (case-insensitive):
 ;	yes|no
 ;	true|false
@@ -301,13 +366,12 @@ group = root
 ; If it is undefined, it is assumed to be no.
 iso = yes
 
-; Build a "mini-USB" image? Same concept as the ISO file
-;	but this can be dd'd onto a USB thumbdrive for the
-;	same effect.
+; Build a "mini-USB" image? Same concept as the ISO file but
+; this can be dd'd onto a USB thumbdrive for the same effect.
 usb = yes
 
-; What URI should iPXE's EMBED script use?
-; DO NOT USE A ',' (comma); instead, replace it with:
+; What URI should iPXE's EMBED script use? DO NOT USE A
+; ',' (comma); instead, replace it with:
 ;	%%COMMA%%
 ; If you require HTTP BASIC Authentication or HTTP Digest
 ; Authentication (untested), you can format it via:
@@ -315,7 +379,7 @@ usb = yes
 ;	https://user:password@domain.tld/page.php
 ;
 ; This currently does not work for HTTPS with self-signed
-;	certificates.
+; certificates.
 ; 0.) REQUIRED if iso and/or usb is set to True/yes/etc.
 ; 1.) Must be a valid URI understood by minimal versions
 ;	of curl.
@@ -324,15 +388,15 @@ uri = https://bdisk.square-r00t.net
 ; Path to the (root) CA certificate file iPXE should use.
 ; Note that you can use your own CA to sign existing certs.
 ; See http://ipxe.org/crypto for more info. This is handy if
-;	you run a third-party/"Trusted" root-CA-signed
-;	certificate for the HTTPS target.
+; you run a third-party/"Trusted" root-CA-signed certificate
+; for the HTTPS target.
 ; 0.) No whitespace
 ; 1.) Must be in PEM/X509 format
 ; 2.) REQUIRED if iso and/or usb is set to True/yes/etc.
 ; 3.) If specified, a matching key (ssl_cakey) MUST be
-;	specified
+;     specified
 ; 4.) HOWEVER, if left blank, one will be automatically
-;	generated
+;     generated
 ssl_ca =
 
 ; Path to the (root) CA key file iPXE should use.

extra/pre-build.d/root/pre-build.sh

@@ -1,5 +1,8 @@
 #!/bin/bash
 
+# we need this fix before anything.
+dirmngr </dev/null > /dev/null 2>&1
+
 # Import settings.
 if [[ -f /root/VARS.txt ]];
 then

extra/templates/VERSION_INFO.txt.j2

@@ -1,5 +1,5 @@
 Version:        {{ build['ver'] }}
 Build:          {{ build['name'] }}
 Time:           {{ build['time'] }}
-Machine:        {{ build['host'] }}
+Machine:        {{ hostname }}
 User:           {{ build['user'] }}{% if build['realuser'] is defined and build['realuser'] > 0 %} ({{ build['realuser'] }}){% endif %}