Hi, > An errata to change the product composition? That seems weird - we > don't do > that now. This has to be discussed with release engineering then. > > I am not exactly following here. This is not replacing comps > > groups, > > install data only select the groups and the kickstart will do much > > the same > > we do now: Select the default setup for installation. > > But we don't have a single default install class. We have multiple > (or no) > defaults - we have a KDE desktop spin, a GNOME spin, etc. - each of > these > have different defaults. For that other product, we have multiple > install > classes, all of which has different default groups and parameters. We do not do anything like this now either.. Right now anaconda uses default comps. So yes, I was thinking that in this regard each product has it's own repository. And regarding code to explode package. We already have it in place, I use it for driverdisc features. Martin _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
