On Wednesday 20 December 2006 15:52, Bruno Wolff III wrote:
I was discussing two different things here. I have a couple of
machines I
haven't really updated to FC6 yet, and had been doing test installs to play
around with respins on test partitions. I figured when I did the real
install I could use the respin with the updates already included. It won't
really save me anything in my case, since I have the update rpms available
on one of the machines already. The second case, was I might be doing some
test FC7 installs before the release in test partitions to help test
things. When I was thinking about doing this for FC5, I thought it would be
nice to try the test install with the latest development rpms, rather than
applying updates after installing with the test iso. I gave up for FC6, but
I might try it again for FC7.
For your second case, why not use the boot.iso that gets generated each night
and install from network? Why start with isos that are old?
> > On sort of a related note, is the Pungi project going to
just support
> > doing respins on the original package set, rather than being able to
> > support respins using updated packages?
>
> Pungi spins with the latest packages it finds in the repos you provide.
> Its all a matter of what repos you provide.
Does this imply, that it isn't in Pungi's charter to worry about
incompatibilities with anaconda and other packages? It just does the spins,
but the user has to make sure the repositories are compatible with anaconda
and each other?
To some extent, yes. Later on I'll be adding some "tree sanity" checking
code
to pungi, or accepting patches that add such things, so that once composed
the tree can get a once over for things like broken deps or other silly
things. If things are too far incompatible, the compose will fail due to
anaconda not being able to run correctly to generate the images.
--
Jesse Keating
Release Engineer: Fedora