On 04/23/2009 04:04 AM, Tom Lane wrote:
Gerry Reno <greno@xxxxxxxxxxx> writes:
I wish that the mirrors could run two repos, one online, one offline and
just switch between them with a pointer. That way they would always
appear consistent to clients. Whenever a big sync would happen it would
happen to the offline repo and once it was finished then the offline
repo would become the online repo. 100% consistency.
I don't think it's that easy ... updates that are in progress are still
likely to see issues. For instance, the package list you pulled ten
minutes ago might say foo-1.2.3 is current, but by now the one that's
visible on http is foo-1.2.4. This is presumably soluble (eg, maybe
keep recently-obsoleted packages on-line for awhile), but it's certainly
not as simple as swapping a top-level symlink.
It's much simpler. You just do the update in 2 passes
- first you download the new packages # old content is there, old
repodata is there, so no breakage
- second you download the repodata and delete old content #content is
already there, new repodata will point users to it.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
