Hi, > 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. Yes, but this information should be based on what you are installing not on from which build you got the installer. > 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? See my answer to Bill about versioning stuff.. Martin _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
