On Sat, 20 Jun 2009, Karanbir Singh wrote: > The way we ship centos-release right now, it only 'sees' the latest > release, so in the CentOS-5 tree, at the moment you can only 'see' > 5.3/ How would that play out with the current habit of soft-linking 5.2/ to 5.3/ when 5.2 content disappears from the mirrors ? Right now, this forces an update to 5.3 when the content is removed. Is the old content going to be kept on the mirrors or only on vault ? Is then vault able to take the load ? > yum --enablerepo=base-5.2 --enablerepo=updates-5.2 --show duplicates > list kernel I vote for this one. While more complicated, it also allows queries of 'give me only release packages' with something like: yum --enablerepo=base-5.2 --enablerepo=base-5.1 --enablerepo=base-5.0 --show duplicates list kernel This is also simpler to maintain, as the metadata would not differ from the one which exists when f.e. 5.2 is declared obsolete. The base+updates solution would require regenerating metadata. -- Bogdan Costescu IWR, University of Heidelberg, INF 368, D-69120 Heidelberg, Germany Phone: +49 6221 54 8240, Fax: +49 6221 54 8850 E-mail: bogdan.costescu at iwr.uni-heidelberg.de