maybe a line in the ebuild that displays on screen when the ebuild is copleting the command that runs the app or whatever was jsut emerged, cuz it's not always easy to figure out what command runs a just installed app and the man pages isn't always the name of the emerged app
you could use qpkg tool that is part of gentoolkit `qpkg -l <pkg>`
This would be appropriate info when we add more extensive documentation to the Portage tree... (future project)
Follow-up: optional XML documentation to live in /usr/portage/cat/pkg/pkg.xml would solve this.
would the optional XML documentation to live in /usr/portage/cat/pkg/pkg.xml include names of the biniaries of deps that were installed as well, or jsut the names of the bianries for the package that was called?
Is this still planned ? Also, would pkg.xml be an extension to metadata.xml or a new file ? Personally I don't see a need for this, `qpkg -l pkg | grep bin/` is IMO sufficient. If there are no objections I'll close this as WONTFIX.
There were no objections and this bug was inactive for more than 3 months. Closing as WONTFIX. Reopen if needed.
