James Bowes wrote:
On Thu, Nov 15, 2007 at 11:22:42AM +0100, Tim Lauridsen wrote:
I have created at patch to add skip-broken functionality to YumBase.

While I'm not against adding skip-broken to core yum, or other things
like downgrades and pinning (though others may disagree ;) ), I don't
know how comfortable I am adding features to the depsolver right now vs
hardening the existing behaviour and speeding it up.
I agree we should not make to drastic changes to the depsolver, but work on hardning and make more testcases . But have not changed the behavior of the the depsolver, i have just a added some code to collect the po with problems and not just the error messages. I could maybe even be useful in some testcase, to be able to test what packages there is failing. The skip broken functionality is implemented in YumBase.buildTransaction and is disabled by default, i was not my plan to activate it or make it available in yum-cli yet.

This raise some questions where we want to go with the yum devlopment:
* What do we want add to the current 3.2.x
* When do we want too make a new unstable branch and what feature do we want to add.

Brainstorming:
  * better, cleaner, faster depsolver.
* more unittest testcases, not only the lowlevel API but also the highlevel stuff (YumBase: update, remove, install etc)
  * http://wiki.linux.duke.edu/YumTodo
* cleanup the logging and make it more simple (do we need all that logging levels, something like quiet, normal, verbose, debug should be enough (--quiet, -v -vv ) * cleanup the API and maybe move some code from yum-cli to YumBase to make it easier to use the Yum api, without needing a lot of code from yum cli. * yum gui api to make it easier to use yum api from gui apps. (http://fedoraproject.org/wiki/TimLauridsen/YumGuiBackBone)
  * Document the API.
  * Localization
  * Multiarch handling, sould it be different than today.
  * Add your own ideas here.
  * And here too

Tim
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel

Reply via email to