> > > product.img: What prohibits us from doing the same as with the > > > updates.img? The two are arguably really about the same thing - making > > > modifications to the stage2 image. The product.img just modifies the > > > available installclasses. That's still modifying anaconda's source > > > files if you think about it. > > > > Yes, but logically, a product.img is more related to your packages than > > to your installer. Maybe this is just the sign that we need to blow up > > install classes like I've been threatening to do for years. > > Well I can certainly just remove the code to download them and then > you'll have no choices besides fixing product.img or hoping no one ever > asks for it back. product.img's are quite useful for creating custom spins w/o needing to run a full buildinstall. In our case, we automatically generate them to provide custom .buildstamp, installclass, and pixmap files. -Kay _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
