Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <093e01c1745c$aece3f50$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT sources DOT redhat DOT com>
Subject: recoverable downloads - opinions sought
Date: Sat, 24 Nov 2001 07:23:15 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 23 Nov 2001 20:23:05.0891 (UTC) FILETIME=[A8AE8F30:01C1745C]

To do recoverable downloads we need 2 things.
1) A way to check the file, other than filesize, for integrity. MD5 will
do and IIRC that's already caclulated on sources.redhat.
2) Code to pickup partway through and carry on.

For 2) we can either code it internally, or link statically to something
like libcurl, or call out to wget/curl.

Thoughts/opinions?

My current mental state:
For creating a mirror aka download only, we have to run on a cygwin-free
system with little or no loss of functionality. Imagine someone on a
corporate network with a dedicated 'net' PC, and cygwin not allowed on
that.

Using an external helper, via a bootstrap process will be a lot easier,
but will sacrifice the functionality when on a non-cygwin machine.

So I'm in favour of internal code/static library linkage. A dynamic
library _could_ be used, but we'd ned to treat it as a special case, not
as a standard isntall-and-log package.

The alternative to internal/static code is to go down the path of
splitting setup into two builds, but as we'd _still_ have to get the
download-without-cygwin part right, I see no benefit in this.

Anything I've missed/got wrong?

Rob