On Tue, 2013-10-08 at 22:04 +0000, "Jóhann B. Guðmundsson" wrote: > On 10/08/2013 09:02 PM, Bill Nottingham wrote: > > The anaconda installation image is made from the tree that it's composing > > from. As long as that's shifting underneath anaconda (file locations, > > NetworkManager interfaces, library bumps, LVM featuresets, etc. etc. etc.), > > considering anaconda behavior and code 'frozen' at branch time is > > extremely impractical when everything it depends on is not. > > I would assume not if we stick to the "GA tree" but more to the point > why exactly does the installation image have to be made from the tree > it's composing from? Well, for a start, if it isn't, we're effectively back to the old situation that we hated, where we have *two* network management code bases to support, *two* initrd frameworks to support, etc etc etc. For each release we'd have the 'live one', and the old 'stable' one that anaconda was based on. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net http://www.happyassassin.net _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
