1 |
As someone whe often does edit ebuilds in overlays (very occasionally in |
2 |
/usr/portage, too), having to run something to update the cache for said |
3 |
overlay is OK. |
4 |
|
5 |
But it *must* update just the cli-specified overlay(s), w/o having to go |
6 |
through and update everything every time it is run. |
7 |
|
8 |
For comparison, my primary workstation, with several overlays, takes |
9 |
several minutes to do a dep. Even with a hot cache. Improving that to |
10 |
something reasonable is the single most important change portage can get. |
11 |
|
12 |
Also, if /var/db/pkg is to be cached, the existing /var/db/pkg layout |
13 |
should remain as a backup, so that the cache of what is installed can |
14 |
be restored easily should it ever get corrupted. Portage can update |
15 |
that cache after updating the /var/db/pkg/ tree. |
16 |
|
17 |
-JimC |
18 |
-- |
19 |
James Cloos <cloos@×××××××.com> OpenPGP: 1024D/ED7DAEA6 |