Jeremy Katz wrote:
On Friday, March 20 2009, Gerry Reno said:
Jesse Keating wrote:
On Fri, 2009-03-20 at 12:03 -0400, Gerry Reno wrote:
The need to make sure that you update rpm or yum before you do 'yum
update' has happened before and I'm sure this isn't the last time
that it will happen either. It just makes sense for a packager to
see if there is an update to itself first. Update itself and THEN do
the updates for everything else.
That's your opinion. The opinion of the people writing the update tools
and preparing the repos and living through such "needs" and really
understanding what is actually going on don't share that opinion.
What is the matter with yum doing something like this?
if updated yum or updated rpm is available:
if updated yum is available:
update yum
yum_is_new = true
if updated rpm is available:
update rpm
if yum_is_new:
sys.execv("/usr/bin/yum", sys.argv) # replace current process
with updated yum
New yum may depend on new python, new glibc, etc and thus 'update yum'
may essentially be 'update everything'
Jeremy
Ok, understand that. So an update of yum has to be left until the
very last moment just before other things that require it.
So maybe change the first line to:
if found package that requires new yum or rpm and updated yum
or updated rpm is available:
That way yum wouldn't update yum/rpm unless something actually required
the updated yum/rpm.
My interest was just to make the process as simple as possible.
Regards,
Gerry
|
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
