| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Mike Auty schrieb: |
| 5 |
> Finally there are overlays, and since these can change outside of an |
| 6 |
> "emerge --sync" (as indeed can the main tree), you'll have to reindex |
| 7 |
> these before each search request, or give the user stale data until they |
| 8 |
> manually reindex. |
| 9 |
|
| 10 |
Determining whether there has been a change to the ebuild system is a |
| 11 |
major point in the whole thing. What does a great index serves you, if |
| 12 |
it does not notice the changes the user made in his own local overlay? |
| 13 |
:) Manually re-indexing is not a good choice I think... |
| 14 |
|
| 15 |
If somebody comes up here with a good (and fast) solution, this would be |
| 16 |
a nice thing ;) (need it myself). |
| 17 |
|
| 18 |
Regards, |
| 19 |
René |
| 20 |
-----BEGIN PGP SIGNATURE----- |
| 21 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 22 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 23 |
|
| 24 |
iEYEARECAAYFAkkp0kAACgkQ4UOg/zhYFuAhTACfYDxNeQQG6dysgU5TrNEZGOiH |
| 25 |
3CoAn2wV6g8/8uj+T99cxJGdQBxTtZjI |
| 26 |
=2I2j |
| 27 |
-----END PGP SIGNATURE----- |
Archives