http://bugzilla.novell.com/show_bug.cgi?id=571690
http://bugzilla.novell.com/show_bug.cgi?id=571690#c2
Ricardo Cruz changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rpmcruz@alunos.dcc.fc.up.pt
--- Comment #2 from Ricardo Cruz 2010-01-19 10:02:49 UTC ---
Repositories do make such information available. RPM fields such as provides,
requires, recommends, suggests, etc are all made available so that Zypp
SAT-Solver can e.g. evaluate beforehand if all its dependencies can be
satisfied.
Alberto had already mentioned this to me. It seems that in the case of
libraries, interpreters and many others, the "provides" field is a nice (if not
fool-proof) to find the more relevant files. For instance, a package like SDL
would have the string "libSDL.so" under provides, or sun-java and gcj would
have the string "javac".
I had already put this feature request under the wiki so I wouldn't forget:
http://en.opensuse.org/YaST2-GTK_brainstorm . Meanwhile, I've also worked on
our Zypp wrapper so to make adding such new search fields much easier:
http://groups.google.com/group/yast2-gtk/browse_thread/thread/c667ebe95c096d...
I think, like yast2-qt, we should simply add a new "provides" option to the
search field (and maybe a "requires" one). Alternatively, we could make the
"filename" option search in "provides" for not-installed packages (and have
some tooltip saying filename search on not-installed is not reliable). But that
could confuse the more advanced users (or could it?).
Maybe the best approach is to have a tooltip on filename search saying:
"filename search can only be performed for installed packages. provides search
can be a satisfactory alternative for not-installed packages however."
At the very least, we want to have this information on the help box. I don't
think many people realize that a provides search can be a good alternative to
the filename one.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.