1 |
The modification date of /usr/portage and overlays dir can be used as a |
2 |
signal for emerge to drop some caches. In this case the drop cache command |
3 |
could just do "touch <dir>", and utils, modifying tree(e.g. "ebuild |
4 |
<ebuild> manifest") could do this operation as well. |
5 |
|
6 |
Best, |
7 |
Alexander Bersenev |
8 |
|
9 |
|
10 |
|
11 |
2013/4/27 James Cloos <cloos@×××××××.com> |
12 |
|
13 |
> As someone whe often does edit ebuilds in overlays (very occasionally in |
14 |
> /usr/portage, too), having to run something to update the cache for said |
15 |
> overlay is OK. |
16 |
> |
17 |
> But it *must* update just the cli-specified overlay(s), w/o having to go |
18 |
> through and update everything every time it is run. |
19 |
> |
20 |
> For comparison, my primary workstation, with several overlays, takes |
21 |
> several minutes to do a dep. Even with a hot cache. Improving that to |
22 |
> something reasonable is the single most important change portage can get. |
23 |
> |
24 |
> Also, if /var/db/pkg is to be cached, the existing /var/db/pkg layout |
25 |
> should remain as a backup, so that the cache of what is installed can |
26 |
> be restored easily should it ever get corrupted. Portage can update |
27 |
> that cache after updating the /var/db/pkg/ tree. |
28 |
> |
29 |
> -JimC |
30 |
> -- |
31 |
> James Cloos <cloos@×××××××.com> OpenPGP: 1024D/ED7DAEA6 |
32 |
> |
33 |
> |