checking for SHELL_CORE... configure: error: Package requirements (gtk+-2.0 >= 2.6.0 libgnomeui-2.0 >= 2.6.0 gnome-vfs-2.0 libglade-2.0 gconf-2.0 poppler-glib >= 0.5.0 gnome-keyring-1 >= 0.4.0) were not met: Requested 'gnome-keyring-1 >= 0.4.0' but version of gnome-keyring is 0.2.0 So I suggest to use ">= gnome-keyring-0.4.0"
There is no gnome-keyring-0.2.0 in portage. 0.4.2 is the lowest available version.
What about an old system like one I have? I still think an ebuild should describe dependencies as exact as possible, not because of the current portage.
That's not my understanding of how it's supposed to work. In this case, for example, there was no gnome-keyring that didn't satisfy the constraint in portage when the dep was added. It's not like I took the >= away, it never existed. I think when a new dep is added to a new version of a package, it's reasonable to assume people have up-to-date portage trees.
