| 1 |
Dan Douglas <ormaaj@×××××.com> wrote: |
| 2 |
> |
| 3 |
> However most of these are only metadata/md5-cache files |
| 4 |
|
| 5 |
By default, eix reads its information for the main portage tree |
| 6 |
from this directory. Check whether e.g. the portage versions |
| 7 |
displayed by eix match which the versions in that directory. |
| 8 |
|
| 9 |
If this is the case (as I suppose) you have perhaps switched to |
| 10 |
git syncing without generating/fetching metadata information |
| 11 |
after syncing: You have to call e.g. egencache with appropriate |
| 12 |
arguments to generate the metadata, at least for the gentoo repository. |
| 13 |
|
| 14 |
Similarly for the overlays, although the situation is more complicated |
| 15 |
there, and by default eix uses other (problematic) methods unless you |
| 16 |
override by setting OVERRIDE_CACHE_METHOD or CACHE_METHOD correspondingly |
| 17 |
(see eix manpage), because for overlays it can be complicated to generate |
| 18 |
the metadata (e.g. if they have an inappropriate .gitignore or use a VCS |
| 19 |
which does not have an analogue of .gitignore). |
| 20 |
|
| 21 |
One passibility to call egencache automatically after syncing is to |
| 22 |
use /etc/portage/repo.postsysnc.d |
| 23 |
|
| 24 |
app-portage/portage-postsyncd-mv (from the mv overlay) will install |
| 25 |
some files which will generate the metadata (also for the overlays - |
| 26 |
depending on your configuration). |
Archives