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