On Thu, Oct 10, 2013 at 10:26:40AM +0000, "Jóhann B. Guðmundsson" wrote: > On 10/10/2013 08:07 AM, Adam Williamson wrote: > > > 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. > > -- > > Restating what has been previously mentioned does not help anything and > comparing the rewrite of Anaconda to the old code base neither. > We need to identify which of the components Anaconda ( still ) uses > that prevent Anaconda from being developed in it's own release cycle. > Like for example which "features" of dracut/systemd/network manager > it's using ( I thought the rewrite move to standalone tools and > libraries ( blivet to handle storage,pykistart etc ) would have made > this easier not harder ) in any case once those components have been > identified we can check those components for api changes and their > changelog for anything else to better see how invasive their changes > are > JBG Asking what tools, libraries, or "features" of tools or libraries are used by anaconda that prevent it from being developed on its own schedule is pointless. Any change in a system component that we use will necessitate change in the installer. This is the nature of installer development. Identifying "features in dracut or systemd" gets you nowhere when those tools vanish and are replaced by entirely new tools. If you want the installer to run on the OS it is installing, development of the installer has to be after everything else completes -or- (like what we do) try to run along side everything else changing and hope for the best. Of course, we could throw all that out and develop our own platform on which to run the installer, which is something we have tried to get away from over the past 5 years (at user request, no less). So you can't now say that "it takes too long" when we have to--at the very least--update the installer to now work with the thousands of little changes that happened since the last release. Remember, we can't release updates via the bodhi firehose like other components. Our releases are Fedora releases. To answer your question, look at the Requires: entries in the anaconda spec file. -- David Cantrell <dcantrell@xxxxxxxxxx> Manager, Installer Engineering Team Red Hat, Inc. | Westford, MA | EST5EDT _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
