Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	RE: Why do we need a mirroring tool - setup.exe based or not?
Date:	Tue, 30 Apr 2002 19:24:26 +1000
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
Message-ID:	<FC169E059D1A0442A04C40F86D9BA7600C5F57@itdomain003.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	"Max Bowsher" <maxb AT ukf DOT net>, <cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g3U9OrR03812

> -----Original Message-----
> From: Max Bowsher [mailto:maxb AT ukf DOT net] 
> Sent: Tuesday, April 30, 2002 7:13 PM

> i.e. they will not want [prev] packages once the superceding 
> [curr] package has proved itself.

And how do you test that? 
 
> Perhaps I'm missing something obvious, but surely setup.exe 
> is all we need?

What if you want a local repository with consolidated dirs for
distribution of cygwin within a corporate LAN?

What if you want to download all packages matching (.*Xfree.*)?

What if you want all curr and prev packages kept cached, but older than
that deleted automatically?

I'm sure there are more examples.

Download only mode is a primitive form of mirroring. If we had a good
mirror tool, we could -consider- removing download only mode completely.

The problem is that setup is aimed at *installing* cygwin. The
maintenance functionality has grown ontop of that base. I'm refactoring
as fast as I have time to, but the guts of setup still reflect that
origin. Everything we do that makes setup more 'complete' makes it
bigger. This isn't good. 

Finally, I'd like to see a much smaller setup that has nearly no
options, and kickstarts the process by downloading cygwin1.dll, a
setup.exe that can call out to libraries, and any core support files for
that. Then from there you can install anything you want. The point being
that the absolute minimum is quite small, and is non-optional.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -