On Thu, 2012-07-12 at 14:35 -0400, David Cantrell wrote: > I understand you've declared this as temporary > and not the ideal solution, but something we can do now to make > progress. > The problem with that is that there's no such thing as temporary here. > We'll carry the hash forever and then a year+ down the road, something > won't > work with arm kernel installation and it'll be declared an anaconda > problem > and we won't have any idea why. And it'll come back to this hash > being out > of sync or wrong or whatever. In fact, the reporters will likely > refer to > it as a "regression" or something "anaconda does that just doesn't > make > sense". So I want to stop that from ever happening in the first > place. +1 That way you never need a "Polishing day" https://www.redhat.com/archives/anaconda-devel-list/2009-February/msg00054.html Matt _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
