Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
From: "Robert Collins" <robert DOT collins AT syncretize DOT net>
To: <cygwin-apps AT cygwin DOT com>
Subject: Setup and cached data.
Date: Sat, 15 Jun 2002 22:21:01 +1000
Message-ID: <002501c21467$1d11ad80$0200a8c0@lifelesswks>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

I've disabled the cache-disabling code in setup in HEAD. This allows
even speedier retrieval of setup.ini|bz2 files when they have not
changed recently. I'm doing this on the theory that folk don't need
absolutely the latest-and-greatest ini and package files:

* Ini updates only occur when packages are released: this isn't daily,
and even if it was, the cache TTL logic would check automatically on
files so recent.
* Package files are versioned, any new file will always be a cache miss.

If anyone runs into trouble with this... Please let me know. It
shouldn't cause any issues though.

On a similar note, I plan on adding a 'current-date-stamp' check to
network retrieval, to allow hints for the current version setup has of a
file. I.e. if the last update of the file we downloaded was x, then only
bother with network retrieval for the fiel if it has been modified
since.

That is a longer term goal though... Patches welcome.

Rob