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