Besides the mostly one row description an ebuild should contain a short summary of what the user would be emerging. A list of possible USE variables would be very useful too. Also there should be some reference to where the software comes from originally. Reproducible: Always Steps to Reproduce: 1. 2. 3. Maybe it's a good idea to keep the descriptions file out of portage. This will keep portage small and easier (and faster) to update. Instead, download the descriptions when they're needed. But this really is the choice of the developers.
short summary was discussed on gentoo-dev (look at archives for info) `emerge <pkg> -pv` will show you USE variable information HOMEPAGE is good enough for 'original source location' imo ... we're here to make/support ebuilds, not determine original creator
Yep. Maybe later, but does not fit / is not needed presently.
