One of the things thats been in the pipeline for a long time is yum's awareness of the entire product lifecycle. 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/ - should you need an older kernel or anything from 5.0/5.1/5.2 - that requires going in and fiddling / creating repo stanza's
So what I would like to do is add awareness of these tree's into the centos-release package, but leave them disabled. allowing people to do things like :
yum --enablerepo=5.2 --showduplicates list kernel
however, while that does look quite nice and clean it will fail to give the user what they mostly want. so they will need something like this :
yum --enablerepo=base-5.2 --enablerepo=updates-5.2 --show duplicates list kernel
which is more along the lines of what someone might be looking for - all kernel packages in the current release+updates, and all the kernel packages released in 5.2's cycle.
So, to work around this and to actually create a '5.2' repository we could just have a set of metadata that includes all of 5.2 and 5.2 Updates. Or we can leave it like this, needing people to enable both base and updates if they want a list of all the packages.
Are there any more options ?
Is there any interest in the Extras/ Plus/ repo's being available like this as well ?
also, while we are at it, we can also drop in repo stanza's for debuginfo's and sources. Over the next few weeks I am going to change the way the debuginfo packages are pushed - which will make it possible to push those in sync with the binary packages.
Another related question, targeted mostly at Seth and James - can creatrepo'd metadata contain a baseurl that is on a different host ? Can yum handle that ? if so, we could have the metadata on mirror.centos.org while the older packages can stay at vault.
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.
On Sat, 2009-06-20 at 09:40 +0100, Karanbir Singh wrote:
One of the things thats been in the pipeline for a long time is yum's awareness of the entire product lifecycle. 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/ - should you need an older kernel or anything from 5.0/5.1/5.2 - that requires going in and fiddling / creating repo stanza's
So what I would like to do is add awareness of these tree's into the centos-release package, but leave them disabled. allowing people to do things like :
yum --enablerepo=5.2 --showduplicates list kernel
however, while that does look quite nice and clean it will fail to give the user what they mostly want. so they will need something like this :
yum --enablerepo=base-5.2 --enablerepo=updates-5.2 --show duplicates list kernel
which is more along the lines of what someone might be looking for - all kernel packages in the current release+updates, and all the kernel packages released in 5.2's cycle.
[...]
Are there any more options ?
yum --enablerepo=*-5.2 --showduplicates list kernel
...you could also add stuff to the aliases plugin, Eg.
CENTOS-5.2-BASE --enablerepo=base-5.2 CENTOS-5.2 CENTOS-5.2-BASE --enablerepo=updates-5.2
...then it could be used like:
yum CENTOS-5.2 list kernel --showduplicates
...as a long term. option we'd like to solve this kind of grouping problem with repo. tags (see upstream createrepo/yum). That may not be viable to use for CentOS-5 though, not sure.
[...]
Another related question, targeted mostly at Seth and James - can creatrepo'd metadata contain a baseurl that is on a different host ? Can yum handle that ? if so, we could have the metadata on mirror.centos.org while the older packages can stay at vault.
Yeh, that works and AIUI Fedora koji static repos. use that functionality (so it's tested :).
-
Bogdan Costescu -
James Antill -
Karanbir Singh