From a wolf31o2 email:
- Ability to grab USE from the environment for a machine both before and after USE_EXPAND is calculated
- Ability to ignore environment's USE when doing calculations, such as the easily grabbing the contents of the "system" target with the default USE for a profile
- Ability to list the stable package versions for a given profile
- Ability to list the testing package versions for a given profile
- Ability to list the used USE flags in a given set of packages
- Ability to list the licenses used in a given set of packages (this is especially important as we are seeing more and more packages that we are not allowed to redistribute being used accidentally)
- Ability to list the packages that use a given set of licenses
- Ability to list the dependency tree for packages, even if some of the dependencies are masked by keywords, rather than throwing up the "this package is masked by keywords" error for each one, allowing one to see *quickly* all of the packages that need keyword changes for a particular package to have its keywords changed... fex. "emerge --keywords =kde-base/kde-4.0" should list all of KDE 4.0's dependencies, and anything that is masked by keywords should show up as "~" or something... anything masked by package.mask should show up as "M"... this should have a way of choosing to ignore profile-level masks or not, also... this is just an example, how we actually get the information doesn't matter, so long as we can get it...
- a standardized api to connect to the soft-serve ice cream machine in the developer lounge
