On Tue, 19 Oct 2004, Axel Thimm wrote: > On Tue, Oct 19, 2004 at 10:40:49AM -0400, seth vidal wrote: > > > Already done a few thread steps above (requoted the part). It's not > > > server-side, that's easy. It's ensuring that the client side will > > > work, and also that it won't break all repos. If freshrpms upgrades > > > yum to yum-2.1.x or yum-2.2, a lot of freshrpms users will find that > > > their other "old" yum repos are dead, and they won't have a handle to > > > use them. > > > > Except that I went around to all of the major repository maintainers and > > in most cases convinced them to run createrepo on their repositories. > > Interesting, I have never heard of that action, and I also find that > most repos I currently use lack the new metadata structures. > > Well, I guess you will have this all sorted out. I was just trying to > be constructive. If my arguments don't convince, that's OK, at least > they were heard ;) For WIW i had (earlier) sugested packageing 'yum20' as a separate package (similar to gcc32 etc). There was a period of time during yum-2.1 releases that I wanted to go back to yum-2.0 - due to missing features. I solved this by installing 2.0 from source. But the solution adopted was to merge yum-arch in yum-2.1 - and provide only repository side support for both versions. Now we have the bizzare senario with 'yum-arch' being part of 'yum-2.1.x.rpm' - but it won't won't work with 'yum-2.1.x'. A separate package 'createreop' should be used for 'yum-2.1.x' Now that 'yum20' is a no-no, how about placing 'yum-arch' in a separate rpm - that doesn't get installed by default? Satish
