Jesse Keating wrote:
Well with the no frozen rawhide proposal, from the Alpha freeze point on
there would be such an updates-testing for the pending release, while
rawhide remains the wild west. You could say install F12, then at F13
Alpha jump onto F13 and have the much newer more often content that has
had some testing. Just keep jumping to the next Alpha and you have your
"rolling release" as it were.
How does that differ from the current situation (except for being a
little more bleeding)?
A true rolling release is install-once, update-forever. Yes you can more
or less do this with upgrade-via-yum, but it is still a large chunk of
effort at 6- or 12-month intervals.
Oh, and on a related note, it would be really helpful if it was possible
to enable updates-testing only for certain packages (and when needed,
dependencies thereof) on a permanent whitelist basis.
include=<package> in the yum conf for updates-testing.
Will that also use packages from -testing when needed to resolve
dependencies for something in the include list? Or will it just break?
('man yum.conf' makes it sound like the latter...)
--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
Thank you for reading all the way to this .sig. You may stop reading
now. Really. It is safe to stop. There is no more content. Why are you
still reading?
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
