1 |
On Mon, 13 Jan 2014 16:38:59 +0100 |
2 |
Luis Ressel <aranea@×××××.de> wrote: |
3 |
|
4 |
> On Mon, 13 Jan 2014 15:58:13 +0100 |
5 |
> Tom Wijsman <TomWij@g.o> wrote: |
6 |
> |
7 |
> > Half a minute if you disable backtracking which you don't need. :) |
8 |
> |
9 |
> Which sadly also means that some updates get skipped silently. (Those |
10 |
> which would trigger rebuilds of other packages because of sub-slot |
11 |
> deps, had that case yesterday). |
12 |
|
13 |
Can you give an example of that? |
14 |
|
15 |
Rebuilds don't cause a different solution in the graph afaik; so, I |
16 |
wouldn't see how that would form a big problem. I also think this would |
17 |
still be covered by preserved-rebuild and/or revdep-rebuild afterwards. |
18 |
|
19 |
In any case, I've not been experiencing problems with this; but am |
20 |
interesting to know how this could go wrong, as no backtracking works |
21 |
for me and I hope it will continue to do so. |
22 |
|
23 |
Btw, this also makes me question how proper pkgcore can do rebuilds. |
24 |
|
25 |
> > > Ironically, launching the same emerge command twice, will take |
26 |
> > > more or less the same time. |
27 |
> > |
28 |
> > Determinism results in more or less the same time, that's correct; |
29 |
> > proper benchmarks would show you a similar result. |
30 |
> |
31 |
> I guess he means that the (according to the file sizes) extensive |
32 |
> caching doesn't seem to be of much use. |
33 |
|
34 |
For that, _all_ caching would need to be removed before the first run; |
35 |
when there is a mention of "the same", I doubt this was done at all. |
36 |
|
37 |
-- |
38 |
With kind regards, |
39 |
|
40 |
Tom Wijsman (TomWij) |
41 |
Gentoo Developer |
42 |
|
43 |
E-mail address : TomWij@g.o |
44 |
GPG Public Key : 6D34E57D |
45 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |