Re: Stabilize anaconda development earlier in the cycle.

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

 



Bravo Adam
 
As a person who promotes Fedora around my city, my frustration is that anaconda is behind the released version.
 
 
 
I can provide a simple example.  I have 4 linux installations including 1 of Fedora 18, 2 of Fedora 19 one of Fedora 20 on a computer on which there are other distributions(Fedora 19 play, and my Fedora 19 stable).  Anaconda in the past always created a grub.cfg that omits one or more of the other distributions.
 
 
So, immediately after reboot, I redo the grub.cfg and amazingly, the rebuilt grub.cfg contains what was installed and the missing distributions.  
 
 
Yes, we should have anaconda created from the distribution it is installing.
 
 
 
Regards

 Leslie
Mr. Leslie Satenstein
An experienced Information Technology specialist.
Yesterday was a good day, today is a better day,
and tomorrow will be even better.
lsatenstein@xxxxxxxxx
alternative: leslie.satenstein@xxxxxxxxx
SENT FROM MY OPEN SOURCE LINUX SYSTEM.


From: Adam Williamson <awilliam@xxxxxxxxxx>
To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list@xxxxxxxxxx>
Sent: Thursday, October 10, 2013 4:07 AM
Subject: Re: Stabilize anaconda development earlier in the cycle.

On Tue, 2013-10-08 at 22:04 +0000, "Jóhann B. Guðmundsson" wrote:
> On 10/08/2013 09:02 PM, Bill Nottingham wrote:
> > The anaconda installation image is made from the tree that it's composing
> > from. As long as that's shifting underneath anaconda (file locations,
> > NetworkManager interfaces, library bumps, LVM featuresets, etc. etc. etc.),
> > considering anaconda behavior and code 'frozen' at branch time is
> > extremely impractical when everything it depends on is not.
>
> 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.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net
http://www.happyassassin.net/

_______________________________________________
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