Those features aren't really suitable to be implemented as the gtk
plugin level. But it would be a shame to see them dying, so let's
give them a shot. We can then pass our code to the maintainers of
the appropriate modules.
With regard to the 2nd point about "unneeded dependencies",
the thing is that there will be false positives and false negatives.
The false positives are troublesome, but we can make sure to
display a caveat emptor. Besides, the dependency resolver won't
let the user remove "needed dependencies". We could even
make use of that ourselves by simulating the removal of the
packages we would list to filter the false positives.
I will try implementing this one directly in C++ in the gtk
plugin, because it was frustrating to come up with a test
case in Python.
By the way, not sure if "unneeded dependencies" really
conveys that these are packages that were once installed
as dependencies but no longer serve a function. What about:
* loose packages
* remnant dependencies
* vestigial dependencies
Or the longer expression: "no longer needed dependencies"
:-?
Cheers,
Ricardo
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
Okay, tried to tackle both features: give them a try to
see how well they work.
Svn download:
http://en.opensuse.org/YaST2-GTK#Download
I also improved the text-box that shows up listing the
packages as they are being downloaded and installed.
It shouldn't flicker now, and, if the user scrolls up, then
it won't force a scroll down -- essentially the scroll behaves
like the ones from any decent terminal program.
Please give that one a try too: I only tested it on a small
test case.
Thanks for giving it a try.
Quoting "Atri Bhattacharya" <badsh...@gmail.com>:
> I am using Revision 62971 from svn. Every time I launch the unneeded
> packages window from the Extras menu, the package manager crashes on me
> (whether I run it as root or not). I have attached the strace log for you.
Thanks, but the gdb debugger would be more useful:
gdb --args /usr/lib/YaST2/bin/y2base sw_single gtk
run
(* crash *)
backtrace
That will give us the "call stack", which is the list the system
uses to keep track of all the functions called until that point (and
their arguments).
> The idea looks perfect to me. I was thinking more along having a category in
> the category view (left pane), but if the unneeeded packages is only
> approximate and could lead to problems, I think it is better to make it a
> little more subtle than that. So the present idea looks just perfect to me.
One problem is that it being so slow, we couldn't show the "count number",
as we do for the other categories.
By the way, I don't want to give you false hopes here. In my freshly
installed system, I think the list it is producing is far from reliable. For
instance, for whatever reason, "yast2-pkg-graph" is not being
detected by the resolver as needed by "yast2-pkg". I guess the
reason for that is that it is a "suggested" packaged -- not sure how
to tell it to honor those packages.
I am also seeing some localization packages... I will try to get some
help from the zypp guys...
> The action listing in the package manager when it is downloading and
> installing packages just got a whole lot better! One more improvement can
> made to that as follows:-
Yeah, the progress status is completely broken at the moment.
I think we already discussed that and filled a bug report for that, right?
Anyhow, unlike the text widget, that behavior is outside the scope
of the gtk plugin...