> Actually, this isn't exactly the same. Operating in cache-only mode will > stop yum from fetching header ranges from remote repositories, so it's > only useful for operations not involving modifications of the local db. > > I think it would be useful to have a feature where repomd is kept for a > certain time before yum re-fetches it again. It's particularly annoying > when mirrorlists are used, since a lot of the times the mirrors get out > of sync. I usually do "yum list updates" before doing "yum update" and > often the two operations will not be identical due to yum hitting > different servers. I think implementing the last-modified check in the repomd.xml grab might be the lightest-weight way. If we have a way of checking the last modified timestamp we might be able to use that to make sure yum ignores out-of-date mirrors. thoughts? -sv
