September 2007 - openSUSE Software Management

[softwaremgmt] software manager: provide aid in removing unused libraries (uninstall)
by Maciej Pilichowski 01 Oct '07

01 Oct '07

Hello, Originally posted here: https://bugzilla.novell.com/show_bug.cgi?id=329018 This is typical situation, I install app A but it requires library L. I install both, then it appears I don't need A anymore, so I remove it, but I have no clue what to remove too. From user point of view, it would be great to click on "check for unused software" and SM would show list of unused libraries, so user could easily remove them. Technically I can imagine it could be done by building reverse dependency tree and show all leaves. The drawback of such approach would be in including main apps too :-) Maybe it could be solved by checking if: 1) there is an executable in the package 2) any of the files in the package were accessed lately 3) did user install it explictly or it was SM call (fullfilling requirements) have a nice day, bye -- Maciej Pilichowski -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

4 6

[softwaremgmt] Some Enhancements/ideas to the softwaremgmt
by Sebastian Furdal 13 Sep '07

13 Sep '07

1. have You ever concidered merge "inst_source" "with sw_single" and "online_update"? 2. yast2 should also remeber last size - its anoying - default size of the yast2 is to samll. 3. In "inst_source" there are "missing" buttons (not list!): "refresh all" "On/Off all" and one column - refresh. 4. Why Yuu add "Repository name" into the "add URL" in "inst_source" into the openSUSE 10.3 ? - the old way was better: shorter & faster - more confuse ;). -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

4 3

[softwaremgmt] opensuse-softwaremgmt@opensuse.org
by Sebastian Furdal 12 Sep '07

12 Sep '07

> * Sebastian Furdal <sfurdal(a)ehelp.pl> [Sep 11. 2007 20:59]: > > 1. have You ever concidered merge "inst_source" "with sw_single" and > > "online_update"? > What kind of problem(s) would that solve ? One module - less confuse! > > 2. yast2 should also remeber last size - its anoying - default size of the > > yast2 is to samll. > I guess you're referring to the window size ? Yes, this hack solve the problem in 10.2 http://software.opensuse.org/download/home:/Beineri/openSUSE_10.2/i586/yast… > > 3. In "inst_source" there are "missing" buttons (not list!): "refresh all" > > "On/Off all" and one column - refresh. > Can you please open an 'enhancement' bug for this ? I have menitoned here https://bugzilla.novell.com/show_bug.cgi?id=224119#c12 but thay send me here :) > > 4. Why Yuu add "Repository name" into the "add URL" in "inst_source" into the openSUSE 10.3 ? - the old > > way was better: shorter & faster - more confuse ;). > I guess thats also worth an enhancement request via bugzilla ;-) > Klaus I have menitoned here https://bugzilla.novell.com/show_bug.cgi?id=224119#c12 but thay send me here :) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] zypper output for machine consumption (--xml, --terse, gui front-ends)
by Jan Kupec 05 Sep '07

05 Sep '07

Hi sw managers :O) As zypper matures, it starts to be used by various tools and front-ends. As a fresh example, Thomas Goettlicher and Joerg Kress recently started to use zypper for actually doing the updates in the OpenSUSE Updaters instead of only checking for the available updates. Thomas started to use the --terse option (not implemented at the time) to switch zypper to write the output in XML and consume it by the updater applet to get the list of available updates, to get progress of operation, messages, etc. But not all output was implemented in XML so far, and it is often mixed with normal output. To further enable and ease the adoption of zypper for this kind of use, more work on its output needs to be done: - the output needs to be switchable from user-readable to machine-readable output or quite output. - the machine-readable output must be well defined and documented - these two types of output must not ever be mixed. Either a machine reads it, or a human (well... hm.. :O) - further fix/document/extend the program exit codes - anything else? I think XML is well-suited for the machine-readable output and we should continue using it here. Current tag/attribute set will need to be extended and documented, a DTD will be needed. The --terse option was inherited from rug, but not implemented until Thomas made use of it. I don't know much about how it worked (or works) in rug, though, but i'm sure it did not write XML. I suggest to start using --xml or --xmlout global option instead of --terse in the future. The --terse option can probably be dropped (but left available for the rug compatibility mode and implemented in rug's way). Opinions? Cheers, Jano -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 1