On 11/09/2012 01:10 AM, Vratislav Podzimek wrote: > On Thu, 2012-11-08 at 20:07 +0000, "Jóhann B. Guðmundsson" wrote: >> Can some of you guys enlighten me and explain to me what causes the >> dependency in the installer environment with the packages/release it's >> about to install and why these have to be tied together ( as in the >> installer cannot exist and be run in an isolated environment on it's own >> specific bits untied to the release or package set it's about to install )? > I know you've already seen [1], but I believe it explains a lot because > all these packages have bugs and all of them change. It is a bit > outdated, but a graph for the current status would look almost the same. > > [1] http://msivak.fedorapeople.org/anaconda-openhouse/#%285%29 This is just as much (or more) an argument that the installer should run in the current [old] environment, not in the to-be-installed [new] environment. The current environment is the environment that is more stable, with more experience and support. The bugs tend to be known, instead of newly-discovered by anaconda. Fixes discovered in development of new versions of required packages can be back-ported to the current release. This is called 'maintenance', and it is work, but it is work that is more known and has less risk than new development. And if the installer is going to depend on a new feature in some required package, then that is a strategic risk that is known in advance, and can be factored into the development plan. -- _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
