| 1 |
On 04/12/04 Andrew Gaffney wrote: |
| 2 |
|
| 3 |
> brettholcomb@×××××××.net wrote: |
| 4 |
> > The twirl twirl is cache updating - it happens after any files that |
| 5 |
> > are synced scroll |
| 6 |
> by > and after it says updating cache. Sync isn't the problem. It's |
| 7 |
> cache updating and that > has been brought up in previous threads. |
| 8 |
> Maybe portage NG will address this. |
| 9 |
> |
| 10 |
> Can someone tell me exactly what is going on during a portage cache |
| 11 |
> update? Or do I just need to Use The Source? |
| 12 |
|
| 13 |
Assuming default setup: |
| 14 |
- copy /usr/portage/metadata/cache to /var/cache/edb/dep |
| 15 |
- check mtimes of actual ebuilds (including PORTDIR_OVERLAY) and update |
| 16 |
/var/cache/edb/dep if they are newer than their cache entries |
| 17 |
|
| 18 |
So if you have a big PORTDIR_OVERLAY the cache update will take longer, |
| 19 |
if you use RSYNC_EXCLUDEFROM it will also take longer. |
| 20 |
The cache entries are the values of *DEPEND, IUSE, HOMEPAGE, ... in a |
| 21 |
format that can be accessed without calling bash to parse the ebuild. |
| 22 |
|
| 23 |
Marius |
| 24 |
|
| 25 |
-- |
| 26 |
Public Key at http://www.genone.de/info/gpg-key.pub |
| 27 |
|
| 28 |
In the beginning, there was nothing. And God said, 'Let there be |
| 29 |
Light.' And there was still nothing, but you could see a bit better. |
Archives