...
Previously: the DVD_overlay had:
ks
packagelist
SIMP
GPGKEYS
noarch
All the noarch simp RPMS
arch (ussually usually absent because no arch spec RPMS)
All the arch specific RPMS
Development Key (if development)
New configuration:
ks
packagelist
SIMP
simp (indicating the simp repo)
All the simp RPMs generated during tar build, noarch and arch
GPGKEYS
Dev key or nothing if not a dev build
...
Then it creates the staging directory under the build directory and one directory for each ISO it is building. I am calling this the OS staginf direcotrystaging directory.
The OS staging directory is the top level of what will be the ISO when it is finished. So here it extracts all the OS files from the OS DVD and prunes them. It extracts the DVD_overlay file to this directory (see above waht what is in there). THen Then it copies the files in yum_data/packages to the SIMP directory in the staging directory according to arch/noarch and links the noarch ones under the arch directory and creates the repo in SIMP/arch.
builddir
yum_data
packages.yaml
packages
RPMs downloaded from the internet
aux_packages
any one off RPMs the user puts here.
SIMP_ISO_STAGING
<OS version name> (This is the top level of the brand new ISO to be created)
(There is a lot more data under here but we are not concerned with this, it will all remain as it.)
OS data
SIMP
noarch
simp noarch RPMs (either built earlier or extracted from tar file)
depenedency dependency noarch RPMs (both one off and packages.yaml)
arch
simp arch RPMs (either built earlier or extracted from tar file)
dependency arch RPMs (both one off and packages.yaml)
links to any RPM in the noarch directory
repodata
...
Then it will start creating the ISO in the same manner, creating the staging sdirectory directory and pruning the OS ISO into it. THen Then extracting the DVD_Overlay file (which it in the new format)
Then it will just merge what is under yum_data/packages into staging directory SIMP and run repo create for each directory under SIMP.
...