Tim Lauridsen wrote:
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.
As far as I understood the discussion some months ago yum development is
supposed to happen in only one (stable) branch. This means a new branch is
nothing more than a new version tag.
So you either need to get your changes commit ready in your private
repository or we need to start a real development branch.
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
A lot of valid points. Can you add them to
http://wiki.linux.duke.edu/YumTodo, please? But we now need to actually pick
up some items and get them done.
Florian
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
