Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID))

[Peter Robinson]

On Thu, Nov 1, 2012 at 5:12 PM, Adam Williamson <awilliam at redhat.com> wrote:

> On Thu, 2012-11-01 at 09:32 -0500, David Lehman wrote:
> > On Thu, 2012-11-01 at 13:01 +0000, "Jóhann B. Guðmundsson" wrote:
> > > On 11/01/2012 12:22 PM, Michael Scherer wrote:
> > > > Maybe having some kind of dependencies between feature could also be
> a
> > > > idea. Anaconda requires dracut to not change, so we need a way to
> > > > express this, and a way to avoid changes at the same time. The same
> goes
> > > > for a python upgrade or lots of things.
> > >
> > > It would be good if any of the Anaconda developers could comment what
> > > external components can affect Anaconda and to what extend atleast if
> > > I'm not mistaken these external components can affect Anaconda
> > >
> > > Kernel
> > > Dracut
> > > Systemd
> > > NetworkManager
> > > Changes in comps/packaging group ( rpm/yum? )
> >
> > lvm
> > mdadm
> > btrfs-progs
>
> parted, grub2, everything in anaconda-tools group in comps...
>
>
EFI, and enterprise storage (FCP, iSCSI, FCoE etc).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20121101/a8b32e4d/attachment.html>