Zypper/Bugs For Adoption

From openSUSE

Revision as of 15:13, 2 April 2009

There are lots of ideas about what should be zypper able to do, how the output should look like, and so on. Unfortunately, we don't have resources to code them all. Fortunately, you can help us :O). Here is one way to do it. Check the following list of bugs and pick up one or few that interests (or bothers) you. Fix it and send us a patch :O) Simple, eh? You can also contact the develpers before or while fixing the bug to get help or coordinate the work.

BTW, some of the bugs may need work in libzypp rather than zypper.

WONTFIX

These are the bugs that we're 100% sure we won't get to them in near (and far) future. Most of them are feature requests. Here is the list. If you have a bugzilla account, you can even reopen the bug and reassign it to yourself to indicate that you're working on it.

Sorted Bugs

These are both the bugs that we plan to fix (but with lower priority) and the above WONTFIX bugs. I'll try to sort them by difficulty/level of experience needed to be able to fix them. Here is an unsorted list, and the sorted one follows.

Easy

bug 472517
bug 484806 - pack solver testcases automatically
bug 462697 - recognize repositories also by names, in addition to number, URI and alias.

Somewhat Complicated

bug 395754 - Do not ask for user confirmation before installing in some trivial cases (e.g. the requested string exactly equals the name of the only one package to be installed). This behavior must be configurable via zypper.conf. bug 409370 - --terse global option should enable --quite mode and print tables as simple comma-separated values for machine consumption. Also other output can be adjusted for machine consumption.

Expert Needed

bug 475723 - you will need to know how to create info pages.

See Also

See also this general development information page. You might want to look at these ideas and plans as well (the bottom of the page).