Re: Dependency checking algorithm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jeremy Katz wrote:
On Tue, 2007-08-28 at 11:14 +0200, Alexander Todorov wrote:
I am looking at the horribly slow installation when packages are specified explicitly (look for an old e-mail from Jeffrey Law: Interesting anaconda/yum performance issue).

Jeff then put together a patch for yum based on where I pointed him that
should have gotten this back to where it "should" be.  And that's been
in for a while.

Where can I find/test that patch? Any relevant BZ?
Which version of anaconda/yum?

Anybody can point me to documentation about dependency checking in Anaconda? Most of you will say that this is a yum thing but the problem may be in anaconda not using yum API correctly.

It didn't have anything to do with depchecking; it was purely a matter
of package _selection_ taking a lot more time.

Yes I realized that after reading the code more carefully.



What I've found is this:
When doing @Everything install things end up in YumBase.install which calls ParsePackages -> buildPkgRefDict

On the other hand 'using yum install *' from the console results in
YumBaseCli.installPkgs which uses self.pkgSack.matchPackageNames in this case.

I am not quite sure what are the differences but it seems strange.
Why do we have 2 different function/code paths that essentially do the same thing, install requested packages? Also there seems to be some duplicating code in buildPkgRefDict and matchPackageNames - creating the NEVRA strings. That's yum 3.2.1-4.

Greetings,
Alexander.


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux