Gentoo Archives: gentoo-portage-dev

From: Brian Harring <ferringb@×××××.com>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] Google SoC and "cache sync"
Date: Fri, 03 Apr 2009 23:16:38
In Reply to: Re: [gentoo-portage-dev] Google SoC and "cache sync" by Emma Strubell
1 On Wed, Apr 01, 2009 at 09:01:59PM -0400, Emma Strubell wrote:
2 > And to clarify: the goal of the project is to modify portage so that
3 > instead of fetching all of the ebuilds in the portage tree (or in an
4 > overlay) upon a sync, portage only fetches the metadata and cache info
5 > (via the metadata/cache/ directory) of the tree, and the ebuilds of
6 > packages that are already installed (packages found in the world
7 > file?) And then, additional ebuilds would be fetched only when they
8 > are needed? Or will only metadata/cache/ be fetched upon sync, and
9 > then all ebuilds will be fetched only when they are needed? Am I
10 > completely oversimplifying the project?
12 Curious, have you thought at all about the server side requirements
13 here? The potentially intractable part here is that the tree you're
14 syncing needs to essentially become versioned (same for the cache).
16 In other words, you sync. 30 minutes later you go to do a merge- in
17 that intervening 30 minutes, a new version of the tree is available-
18 but your metadata is 30 minutes old, meaning it's no longer valid.
20 Honestly, that is the part of the problem that needs solving- the fact
21 you need to embed versioning into this to ensure that things are still
22 consistant. Would be curious to hear what you're intentions are for
23 that issue- w/ rsync, it's potentially intractable depending on your
24 intentions.
26 ~harring