| 1 |
On Wed, 05 Nov 2014 17:36:34 +0100 |
| 2 |
hasufell <hasufell@g.o> wrote: |
| 3 |
|
| 4 |
> You were proposing that I strip down the DESCRIPTION field in my |
| 5 |
> ebuild and put the keywords relevant for finding the package into |
| 6 |
> <longdescription> in tag metadata.xml. |
| 7 |
|
| 8 |
No, I was proposing the overly long description should go to |
| 9 |
<longdescription />. As for the DESCRIPTION variable, it looks like it |
| 10 |
can be shortened easily. |
| 11 |
|
| 12 |
<<<Dungeon Crawl Stone Soup is a role-playing roguelike game of |
| 13 |
exploration and treasure-hunting in dungeons |
| 14 |
>>>Dungeon Crawl Stone Soup - a roguelike RPG dungeon crawler |
| 15 |
|
| 16 |
Since it appears to be an actual roguelike (and not merely a game with |
| 17 |
permadeath as is how these days people interpret it) you could actually |
| 18 |
get it down to: "Dungeon Crawl Stone Soup - a dungeon crawler". |
| 19 |
|
| 20 |
> That leads to the question how do you read the longdescription field |
| 21 |
> from metadata.xml via eix or other commonly used tools for finding |
| 22 |
> packages. packages.gentoo.org doesn't allow it either. |
| 23 |
|
| 24 |
packages.g.o simply links to metadata.xml. I guess that works. |
| 25 |
|
| 26 |
|
| 27 |
jer |
Archives