On 11/05/2014 05:27 PM, Jeroen Roovers wrote:
> On Wed, 05 Nov 2014 17:06:52 +0100
> hasufell <hasuf...@gentoo.org> wrote:
>
>> Could you elaborate how to query that field via eix which is the
>> de-facto standard for finding packages?
>
> The official standard for finding packages is packages.gentoo.org. It
> (and the somewhat popular eix) have no problems at all reading
> the DESCRIPTION variable from the actual ebuilds.
>
> # eix eix
> [I] app-portage/eix
> Available versions: 0.25.5 0.29.3{tbz2} ~0.29.6 ~0.30.0 ~0.30.1
> ~0.30.2 {clang debug +dep doc nls optimization security sqlite
> strong-optimization strong-security swap-remote tools
> zsh-completion LINGUAS="de ru"}
> Installed versions:
> 0.29.3{tbz2}(06:55:52 27/05/14)(dep doc nls sqlite -clang -debug
> -optimization -security -strong-optimization -strong-security
> -swap-remote -tools -zsh-completion LINGUAS="-de -ru")
>
> Homepage: http://eix.berlios.de
> Description: Search and query ebuilds, portage incl. local
> settings, ext. overlays, version changes, and more
>
> In this splendidly exemplary case, eix actually read the description
> from the ebuild - its very own metadata.xml does not have one.
>
>
I think you didn't get my question.
You were proposing that I strip down the DESCRIPTION field in my ebuild
and put the keywords relevant for finding the package into
<longdescription> in tag metadata.xml.
That leads to the question how do you read the longdescription field
from metadata.xml via eix or other commonly used tools for finding
packages. packages.gentoo.org doesn't allow it either.
