| 1 |
On Wed, Nov 25, 2009 at 02:50:22PM -0700, Denis Dupeyron wrote: |
| 2 |
> The next council meeting will be on 7 Dec 2009 at 1900UTC. If you want |
| 3 |
> us to discuss things please let us know in reply to this email. What |
| 4 |
> is already known is we'll talk about mtime preservation and prefix. |
| 5 |
> You can find threads about those at: |
| 6 |
> http://archives.gentoo.org/gentoo-dev/msg_a9e26414f2278275bdfa08baf839704f.xml |
| 7 |
> http://archives.gentoo.org/gentoo-dev/msg_2a62689c71f95e4de5699a330b8b5524.xml |
| 8 |
|
| 9 |
I'd like |
| 10 |
http://archives.gentoo.org/gentoo-dev/msg_6b3e00049a1bf35fbf7a5e66d1449553.xml |
| 11 |
to be discussed, specifically zacs form of forced mtime updating of |
| 12 |
/var/db/pkg on vdb modifications |
| 13 |
|
| 14 |
Reiterating the reasoning, it'll be used for enabling the managers to |
| 15 |
manage caches, specifically invalidating said caches if an alternative |
| 16 |
manager modifies the vdb. |
| 17 |
|
| 18 |
End result, if we can build better caches for vdb, vdb access can be |
| 19 |
heavily sped up. |
| 20 |
|
| 21 |
At this point, pkgcore/portage both have it implemented. Not sure if |
| 22 |
portage has released it yet, but >=pkgcore-0.5.2 is in the tree w/ |
| 23 |
said updating support. |
| 24 |
|
| 25 |
~harring |
Archives