<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Bert Freudenberg wrote:
<blockquote
cite="mid:0E62A9BC-23B8-4ADC-8AF3-D787BE810F94@freudenbergs.de"
type="cite">
<pre wrap="">On 10.06.2011, at 22:59, Hannes Hirzel wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 6/9/11, Bert Freudenberg <a class="moz-txt-link-rfc2396E" href="mailto:bert@freudenbergs.de"><bert@freudenbergs.de></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi folks,
I just tried to update an older trunk image to the current one. It took
ages.
</pre>
</blockquote>
<pre wrap="">Bert
Which version was the older trunk image?
</pre>
</blockquote>
<pre wrap=""><!---->
Update config 168.
</pre>
<blockquote type="cite">
<pre wrap="">How long is "ages"? 20 min, 1 hour, 2 hours, 4 hours?
</pre>
</blockquote>
<pre wrap=""><!---->
15 minutes maybe? I didn't watch the clock.
</pre>
<blockquote type="cite">
<pre wrap="">How often are you going to repeat the exercise in the future?
</pre>
</blockquote>
<pre wrap=""><!---->
Not very often.
I guess I'm just spoiled by how snappy the update process usually is ;)
About 50 packages changed since 168.mcm. So ideally the update process would only have to download 50 mcds. Instead, it downloaded about 240, forced by the update maps. Which is still better than downloading all 650 mcds corresponding to each commit individually. And a lot better than downloading full mczs, as Levente pointed out.
So, it's not that bad after all.
- Bert -
</pre>
</blockquote>
How about intermittently auto-downloading available updates but not
installing them. They are just cached locally for whenever an update
is run?<br>
</body>
</html>