Gentoo Archives: gentoo-dev

From: Charles Lacour <gentoo-dev@×××××××.com>
To: "Thomas T. Veldhouse" <veldy@×××××.net>, Christian Skarby <christian.skarby@×××××××××.no>, Mezei Zoltan <mz269@××××××××.hu>, gentoo-dev@g.o
Cc: mz269@××××××××.hu
Subject: Re: [gentoo-dev] Portage suggestion
Date: Tue, 13 Aug 2002 20:57:17
Message-Id: 02081320571200.01798@bugler
In Reply to: Re: [gentoo-dev] Portage suggestion by "Thomas T. Veldhouse"
1 On Tuesday 13 August 2002 11:10, Thomas T. Veldhouse wrote:
2 > I think what the original poster is looking for is the ability for it to
3 > fetch in the background and compile in the foreground. Time to compile
4 > meta-packages like KDE might be reduced significantly, especially on
5 > bandwidth challenged systems. Basically, the fetch should be performed on
6 > a separate thread than the build.
7 >
8 > Tom Veldhouse
9
10 That's the way I read it, too, and I'm fairly sure there's something that
11 does exactly that in beta-testing right now.
12
13 Ok, I found it. It was posted by Nick Jones <carpaski@g.o> on Aug 3,
14 2002, with a subject of "Concurrent download and merge"
15
16 In case you have trouble finding it for whatever reason, here's the text:
17
18
19
20
21 I've been working on code to make downloading occur continuously
22 during the emerge process. I have new, clean, and working code
23 that needs a bit more testing that I can give it. I'd appreciate
24 some testing. It includes a couple subtle enhancements also. Try
25 'emerge -ef world' to see the "(X of Y)" counts.
26
27 At present, the output is a little noisy because wget and builds
28 are happening at the same time. I HIGHLY recommend adding "-q"
29 to wget's FETCH_COMMAND in make.globals/make.conf.
30
31 Please CC me (carpaski@g.o) with any bugs that you think
32 you come across. PLEASE follow the directions in the README.txt.
33
34 http://gentoo.twobit.net/portage/threaded/
35
36 It does as follows:
37
38 1. Downloads begin and do not pause until they are completed.
39 2. Merges occur in order as the required files finish downloading.
40 3. Failed merges will stop the merging of packages at that point,
41    but fetching will continue until all files are downloaded.
42 4. Failed fetches will be announced, but WILL NOT stop the fetching.
43    Merges will continue until the failed fetch is reached. Fetches
44    will continue until all fetches have completed.
45 5. Failures in the fetching and/or failure in the merge will be
46    noted when both the fetching and the merging are completed.
47    Only one notice for the fetches is given. Only one notice
48    of the failed merge is given.
49
50 Thanks,
51 -- Nicholas Jones