do you really need proof to see that the dependency checking is a highly time consuming thing.
i just did a yum update.
i had a 100% cpu usage for a few minutes during the dep checking. that`s _TOO_ much for just a update. (oke.. this is a update of 148 packages but still)
it just seems overkill for me.. specially now that i know that it can all be done in well under a second in a logic way :P
2007/4/11, Ahmed Kamal <
email.ahmedkamal@xxxxxxxxxxxxxx>:
Stepping back again, is dep solving the part that slows down yum? Has anyone profiled yum and identified which part(s) are slowest.On 4/11/07, Olivier Galibert <galibert@xxxxxxxxx> wrote:On Wed, Apr 11, 2007 at 07:03:49AM -0700, Otto Rey wrote:
> Is there any "spec" or "documentation" of version checking and dependency checking?
>
> IMHO to change, add features or reimplement existing tools or projects. we need documentation, like developer-readables-mini-rfc's
> Read source code to extract logic will produce mistake's , specially with different languages.
IME, every developer agrees with that, and no developer wants to write
it. Even worse, when they do write it, the assumptions are often
wrong about what is clear/already known and what isn't. So it's often
better when someone else does the documentation. Which almost never
happens. Add to that the fact that writing good documentation is a
skill by itself.
So, well, UTSL like everybody else :-)
OG.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
