Re: re: another approach to what current does

Just wanted to point out that my intention was not to discredit yum, just to
point my own opinion. Still, my point is that i do not want to deal with
maintaining my own repository, i simply want to copy the one from RHN. And
yum cannot even remotely compare (yet) to the amount of QA put into up2date
(by having redhat deploy it in every machine you install).
 
-------Original Message-------
 
From: [email protected]
Date: éåí ùìéùé 13 àåâåñè 2002 22:26:08
To: [email protected]
Subject: [Current-server] re: another approach to what current does
 
Hey,
Hunter pointed out this thread to me about up2date-client and yum - I
wanted to remark on a couple of points but in general you should use
what you like:
 
[Alex Kramarov wrote ]:
The last email was all about telling me that current/RHN - db = yum. I
have tried yum, and do not accept it as an acceptable platform for
production use One of the reasons is that it's is still in development.
I WANT to have up2date as the client. i DONT TRUST anything else to mess
with system config of my machine. I also want the ability to synchronize
to RHN servers - yum does not provide that. I have to update yum package
repository manually.
 
[ end quote ]
 
1. yum has nicely stolen all the grub and lilo modification code
DIRECTLY from up2date client - I didn't want to write any of that stuff
any more than anyone wanted me to write it :) I stole the code, I import
the functions and use them - directly - and I nicely gave red hat credit
:)
 
2. the only config modifications that occur, occur in the rpm %post and
%pre scripts - yum doesn't modify anything in ANY way that rpm or
up2date doesn't. I'm not making any calls outside of rpm for anything,
that was the whole point. My general feeling is that the less smarts I
attempt to give yum the better off I am :)
 
3. if you rsync the updates dir from any of red hat's ftp mirrors you
can run yum-arch on them in an automated way so the repository is
automatically built - I already do that at:
 
http://mirror.dulug.duke.edu/pub/yum-repository/redhat/updates/7.3
 
typically the suggestion is: rsync, rpm -K, yum-arch -z if the other two
complete.
 
4. Yum is in fairly widespread use at duke now and its going into a
larger testing cycle at fermilab (only about 25-40 machines at fermi
though) It is under development but in the same way that up2date is
under development.
 
 
So I just wanted to bring up those points - not trying to start an
argument.
 
thanks
-sv