Lorax is a set of tools used to create bootable images.
Go to file
2014-05-12 17:23:09 -07:00
docs livemedia-creator: Add support for making tarfiles 2014-04-07 10:58:32 -07:00
etc Remove empty config files 2010-12-08 12:40:46 +01:00
rel-eng Automatic commit of package [lorax] release [21.10-1]. 2014-05-12 17:23:09 -07:00
share runtime-install: Add rpm-ostree, move dnf here 2014-05-12 08:28:56 -07:00
src Add --add-template{,-var} 2014-05-12 16:04:28 -07:00
tests Add pylint testing 2014-05-09 08:10:41 -07:00
utils Cleanup other misc pylint warnings 2014-05-09 08:10:41 -07:00
.gitignore give version.py its own makefile rule and .gitignore line 2011-10-24 19:01:21 -04:00
ANNOUNCE Added draft on initial announce email as I keep adding to it. 2008-10-06 09:51:01 -10:00
AUTHORS add wwoods to AUTHORS 2011-10-26 12:36:06 -04:00
COPYING Initial project description files imported. 2008-09-11 14:16:39 -10:00
lorax.spec Automatic commit of package [lorax] release [21.10-1]. 2014-05-12 17:23:09 -07:00
Makefile Add pylint testing 2014-05-09 08:10:41 -07:00
POLICY Update TODO and POLICY to reflect the current state of things 2012-01-06 14:41:21 -05:00
README Initial project description files imported. 2008-09-11 14:16:39 -10:00
README.livemedia-creator livemedia-creator: Add support for making tarfiles 2014-04-07 10:58:32 -07:00
setup.py Cleanup other misc pylint warnings 2014-05-09 08:10:41 -07:00
TODO Update TODO and POLICY to reflect the current state of things 2012-01-06 14:41:21 -05:00

I am the Lorax.  I speak for the trees [and images].

Tree building tools such as pungi and revisor rely on 'buildinstall' in
anaconda/scripts/ to produce the boot images and other such control files
in the final tree.  The existing buildinstall scripts written in a mix of
bash and Python are unmaintainable.  Lorax is an attempt to replace them
with something more flexible.


EXISTING WORKFLOW:

pungi and other tools call scripts/buildinstall, which in turn call other
scripts to do the image building and data generation.  Here's how it
currently looks:

   -> buildinstall
       * process command line options
       * write temporary yum.conf to point to correct repo
       * find anaconda release RPM
       * unpack RPM, pull in those versions of upd-instroot, mk-images,
         maketreeinfo.py, makestamp.py, and buildinstall

       -> call upd-instroot

       -> call maketreeinfo.py

       -> call mk-images (which figures out which mk-images.ARCH to call)

       -> call makestamp.py

       * clean up


PROBLEMS:

The existing workflow presents some problems with maintaining the scripts.
First, almost all knowledge of what goes in to the stage 1 and stage 2
images lives in upd-instroot.  The mk-images* scripts copy things from the
root created by upd-instroot in order to build the stage 1 image, though
it's not completely clear from reading the scripts.


NEW IDEAS:

Create a new central driver with all information living in Python modules.
Configuration files will provide the knowledge previously contained in the
upd-instroot and mk-images* scripts.


-- 
David Cantrell <dcantrell@redhat.com>