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 Thu, 2012-11-08 at 21:45 +0000, "Jóhann B. Guðmundsson" wrote:
> On 11/08/2012 09:36 PM, Chris Lumens wrote:
> > No, this is absolutely not the direction we will be moving in.
> 
> So which direction do you want to take the installer so we can easily 
> revert it should it become necessary or if the project would like to 
> release updated GA release with an updated installer?

Below is my take. I'm not management, so technically that's all it is.

We already have a focus for current and immediate-future development.
Discussions are fine, but your expectations should be set that we're not
about to change directions now.

> 
> Surely the best method ( and the least effort ) would be to maintain the 
> same installer for all releases ( GA+Branched+Rawhide ) so what 
> different command code template being used based on "detect" release 
> being installed?

We've just been discussing how much work it is to maintain the installer
for one branch. Doing so for three branches sounds like 250% the work of
doing it for one.

> 
> What has been discussed, thrown out there to solve this/these problems?

Fewer branches? Fewer install methods? Fewer install-time configurables?

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


_______________________________________________
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