On Wed, 2011-11-16 at 06:59 -0500, Martin Sivak wrote: > Hi guys, > > I have written a summary of my discussion with dcantrell and dmach from release engineering. > > https://fedoraproject.org/wiki/Anaconda/Features/InstallClassesInRepo > > Might be worth a thought. It's an interesting idea - I like the "when/unless" syntax, too. One question: why store it in a package? This seems a lot like .buildstamp - it's metadata the installer uses to decide how it should run and what options it should present. We could store the various .installclass files (or whatever they would be called) in a package like we do with fedora-kickstarts. In fact, in the future I'd like to see all the bits and pieces that go into making a tree/image (kickstarts, bootloader configs, lorax templates, etc.) collected in one package, with one directory per spin. Having an 'installclass' file in there would be pretty simple, and that'd allow lorax to drop it into the agreed-upon place in the tree. Unless there's some reason it needs to be inside a package in the tree? -w _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
