https://bugzilla.novell.com/show_bug.cgi?id=637211 https://bugzilla.novell.com/show_bug.cgi?id=637211#c2 --- Comment #2 from Ricardo Cruz 2010-09-19 21:53:26 UTC --- Michael, would you like to have a look at the feasibility of this feature request? As we've discussed over the mailing list, we could do something like: unneeded = [] for pkg in zypp.pool(): ...# was pkg installed by the user, or the solver? ...if not pkg.onSystemByUser(): .......# it was installed by solver: check if it is still needed .......needed = False .......for pkg2 in zypp.pool(): ...........if pkg2.requires (pkg): ...............needed = True ...............break .......if not needed: ...........unneeded.append (pkg) --- The Achilles' heel on all this is the method "pkg.onSystemByUser()". Unfortunately, it isn't reliable. It wouldn't matter if it sometimes would falsely return True. That would just mean that our net wouldn't sometimes catch all the "unneeded" fish. My worry is that packages installed by the update applet are marked as if they were installed by the solver. In such cases, "pkg.onSystemByUser()" would falsely return False. Therefor, we could show crucial packages as "unneeded", and wreck the user's system. One potential solution to this is to check if the package was installed from the update repository, "http://download.opensuse.org/update/". We could then assume those packages as being installed by the user. But can the user add other update repository to the update applet, or is this one repository hard-coded? Any other problems I'm not foreseeing? Solutions? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=637211 https://bugzilla.novell.com/show_bug.cgi?id=637211#c4 Ricardo Cruz changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |libzypp AssignedTo|rpmcruz@alunos.dcc.fc.up.pt |zypp-maintainers@forge.prov | |o.novell.com QAContact|jsrain@novell.com |qa@suse.de --- Comment #4 from Ricardo Cruz 2010-09-23 11:13:42 UTC --- I could use some help with the implementation. Anyone from the zypp team interested in taking the bug? My main issue: a) "if pkgA.requires(pkgB) then": how can you test for something like this? Capabilities.h only deals in raw rpm strings; how can you get the processed meat? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=637211 https://bugzilla.novell.com/show_bug.cgi?id=637211#c6 --- Comment #6 from Ricardo Cruz 2010-09-24 17:53:30 UTC --- Good point with regard to patterns. Anyhow, Michael, we need to be able to test for "does pkgA require pkgB ?", otherwise we can't tell if a dependency is still needed. Remember, this is the algorithm we're using: for pkg in pool: .if pkg.isInstalled(): ...if wasInstalledAsADepedency (pkg): .....if not isStillADependency (pkg): .......unneeded += [pkg] My problem is with implementing "isStillADependency()", which I though of doing as: bool isStillADependency (pkg): .for pkg2 in pool: ...if pkg2.requires (pkg): .....return True .return False I don't know what libzypp API to use here, if there's any. Please give me some directions here, because someone foreigner to libzypp can easily lose a lot of time finding his way. Alternatively, I guess we could pull off something like this: bool isStillADependency (pkg): .pkg.remove() .ret = zypp.resolver.resolvePool() .zypp.resolver.undo() .pkg.install() .return ret If it is a dependency, it should require user input, and "resolvePool()" should return False. Michael, thanks for your help, btw! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.