Re: Anaconda and it ties to the release/packageset it's about to install

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/09/2012 07:57 AM, John Reiser wrote:
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.

The "current" environment often cannot run newer hardware, or you run into other oddities where the environment in which you performed the install differs from the environment you're about to boot into and that causes weird and subtle bugs with the system.

We don't do things the way they are now because we like hard problems. We do it because we've had lots of experience showing us that it really is the better way, even though it does make many things harder.

--
Jesse Keating
Fedora -- Freedom² is a feature!

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list



[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux