On Thu, Nov 8, 2012 at 9:19 PM, Bill Nottingham <nott...@redhat.com> wrote: > Matthew Garrett (mj...@srcf.ucam.org) said: >> Patches that cleanly decouple Anaconda from the entire software stack >> that it runs on top of would probably be received with open arms, but >> nobody who works on it has any idea how to implement them. > > In fact, this is what has been done in anaconda over the past couple of > releases - Anaconda migrated from having its own boot and init > infrastructure to using system-provided items such as dracut and systemd. > But that's complicated work, and while you're doing that migration, you're > doing a lot of arbitration as to what bits are in generic dracut, what > bits are in generic systemd, and what bits remain in anaconda. And during > that process, you are *very* tied to the version of the underlying system, > until the work is fully complete and there is a defined separation of > features into each layer. > > This, incidentally, also is why running the F17 installer on F19 isn't > practical.
Well not practical maybe ... impossible no. In fact making an isolated image using F17 components and installer to use it to install F18 should work. SB would be an issue though because the old anaconda does not know anything about it, -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
