Hey Jason,

	As you know, I'm currently working on a tool to manage /etc/portage
easily, to help users.  Tentatively named emod, it has the synopsis 

emod mask|unmask|keyword|inject [--include-deps] [--category] blah1
blah2...

Well, for the first optional argument, emod needs access to portage's
dependency information.  It would need to know what versions the package
depended on, whether those packages could be sastified by "keyword"
instead of "~keyword", and if emod is at one point extended to combine
the functionality of euse, ie adding an |use mode, it would also need
access to every package's dependencies IUSE settings to determine
whether or not the given use was valid for deps.

Thats all I can think of for right now, if I come up with more I'll let
you know.

Mike Tindal