On Fri, 2008-09-26 at 14:31 +0200, Patrice Dumas wrote: > I understand that for installs/upgrades using anaconda, thus for images, > but for users that track rawhide, being able to test if bugs are fixed > without doing a local rebuild is handy. Especially for packages that are > not at the core of the distribution. I guess that maybe it isn't very > practical, but the frozen packages in rawhide could be a subset of the > packages, including everything in the minimal buildroot, in some groups, > say @base, @base-x, @code, @fedora-packager, @hardware-support, > @input-methods, @legacy-software-development, @legacy-software-support, > @printing, @system-tools, and their dependencies, and the kernel > (and maybe @admin-tools). Not really practical, bound to be wrong. Instead we offer static-repos of the continued package flow for those people who want to bypass any testing of the freeze content. Those repos aren't mirrored just yet, and may be in the future, but with our current resources available, the best way to get things done is to freeze rawhide. -- Jesse Keating Fedora -- Freedom² is a feature! identi.ca: http://identi.ca/jkeating
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
