zero@ozzie libgnome-keyring % depcheck libgnome-keyring * Checking gnome-base/libgnome-keyring-3.12.0 for undeclared dependencies * /usr/lib64/libgnome-keyring.so.0.2.0 links to /usr/lib64/libgobject-2.0.so.0 * Missing RDEPEND on dev-libs/glib * /usr/lib64/libgnome-keyring.so.0.2.0 links to /usr/lib64/libglib-2.0.so.0 * Missing RDEPEND on dev-libs/glib * /usr/lib64/libgnome-keyring.so.0.2.0 links to /usr/lib64/libgcrypt.so.11 * Missing RDEPEND on dev-libs/libgcrypt When I upgraded libgcrypt I got a preserved-lib warning for libgnome-keyring. I went to add := to the libgcrypt dep but it seems to be missing entirely. Depcheck shows some others as well. Please fix as you see fit.
+ 14 Oct 2014; Pacho Ramos <pacho@gentoo.org> -libgnome-keyring-3.10.1.ebuild, + libgnome-keyring-3.12.0.ebuild: + Fix missing dependencies (#522526 by Rick Farina (Zero_Chaos)), drop old + Thanks. Where does that "depcheck" utility come from? Maybe would be useful for us :)
(In reply to Pacho Ramos from comment #1) > + 14 Oct 2014; Pacho Ramos <pacho@gentoo.org> > -libgnome-keyring-3.10.1.ebuild, > + libgnome-keyring-3.12.0.ebuild: > + Fix missing dependencies (#522526 by Rick Farina (Zero_Chaos)), drop old > + > > > Thanks. Where does that "depcheck" utility come from? Maybe would be useful > for us :) It's in the qa-scripts repo. I'm cleaning it up to avoid the false positives and some of the more annoying messages. The plan is to actually merge it in piece by piece into portage FEATURES=QA. If you want to use it now, you can catch myself or kensington on irc. It needs love, but overall it's more useful than annoying :-)
