On Wed, Dec 05, 2012 at 09:39:41PM -0800, Adam Williamson wrote: > > I think that may be the case _now_ with our current Anaconda situation, but > > the more I think about it, the more strongly I feel about making this the > > approach for future releases. When there's _not_ a big Anaconda rewrite, > > kickstart commands shouldn't change drastically without planning. So, I > > don't think it's unreasonable in the real world. > The commands themselves shouldn't change, but it's certainly possible - > and frequently happens - for something to change in anaconda or some > layer below anaconda which happens to have the effect of breaking a > kickstart directive. ... which should be a blocker. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
