Open dirtyharrycallahan opened 10 years ago
makes sense to me, @dirtyharrycallahan. patches welcome!
I'll have to think about this one some more - they are tied together in several places -in the kickstart (stig-fix.cfg) the stig-fix rpm is installed on line 167, but actually called the graphical configuration (menu.py) in the 'configure_system_profile' function on line 425 - it's not as easy as just adding in a path. I'm fully expecting users to create their own RPMs using the ability I've added to stig-fix-el6 in 1.7.7 and customize this kickstart for their own needs (e.g. automatically registering a system with RHN Satellite via an activation key and rhnreg_ks)...
The idea is to not have to include the banner code and rpm in this project but specify a path when creating the ISO. The ISO would work as it does now it just sources the needed file from the other two projects based on command line options.
Let me see what I can do this weekend - I'm looking for atomic commits that are easier to track.
Users should be able to specify a path to classification banner and the stig rpm so they do not have to be included in this project. I would be willing to submit a pull request.