Lorax is a set of tools used to create bootable images.
Go to file
2008-10-04 19:53:33 -10:00
etc Forgot to delete etc/packages.ppc64 2008-10-04 17:57:12 -10:00
rewrite Remove more of buildinstall that has been rewritten. 2008-10-04 19:07:32 -10:00
share Start populating the share directory. 2008-10-04 19:43:27 -10:00
src Rename lorax.py to lorax. 2008-10-04 19:50:56 -10:00
.gitignore Ignore *.pyc files. 2008-09-12 12:10:33 -10:00
AUTHORS Initial project description files imported. 2008-09-11 14:16:39 -10:00
COPYING Initial project description files imported. 2008-09-11 14:16:39 -10:00
Makefile Write Makefile and correct problems in setup.py. 2008-10-04 19:51:17 -10:00
POLICY Update the POLICY file. 2008-10-03 15:45:33 -10:00
README Initial project description files imported. 2008-09-11 14:16:39 -10:00
setup.py lorax.py -> lorax 2008-10-04 19:53:33 -10:00
TODO Add -c option to allow user to specify confdir. 2008-10-04 19:06:21 -10: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>