On Fri, Jun 06, 2003 at 01:54:57PM -0400, seth vidal alleged: > > > The primary difference, from a user's perspective, is that yum updates > > it's local headers everytime it runs. The urpmi headers must be updated > > manually with 'urpmi.update'. Very generally speaking, if you are doing > > one operation, yum is faster; if you are doing several operations, it's > > nice to update *once* with urpmi. > > > > 'yum list' is slower than 'urpmq -y' > > is 'yum -C list' slower? I'm curious. Yes, a lot slower. In 5 tries, 'yum -C list glibc\*' was between 6.5 and 7.0 seconds. Also in 5 tries, 'urpmq -y glibc' never took longer than .5 seconds. But this understandable. yum does a lot more every time it runs. Also, -C doesn't change anything, it still takes the same amount of time to run. > > yum has "install" and "upgrade" commands, urpmi doesn't differentiate > > between the two (which is a behaviour I prefer). > > so I looked through the urpmi code when I first heard about it - > > how does it handle obsoletes or mutual obsoleting packages? > > It doesn't seem to have any special allowance for them. Which seems odd. > > I couldn't find anything about them in the code but I only scanned > through it a few times. I know that it does handle obsoletes because I've seen it happen. But I'm really the wrong person to ask *how*.
